Flectar develops and maintains software and digital infrastructure, including open-source projects that handle sensitive information, authentication, and untrusted external content.
Our approach focuses on reducing attack surfaces, protecting user information, reviewing security-sensitive code, and identifying and remediating vulnerabilities in systems we own or maintain.
Security leadership
Tomás leads security engineering, vulnerability management, and defensive security work across Flectar-maintained software and infrastructure.
The security function includes reviewing security-sensitive architecture and code, investigating potential vulnerabilities, validating fixes, coordinating responsible disclosure, and overseeing security-related contributions from authorized collaborators.
- Security contact
- security@flectar.com
- GitHub
- github.com/iamdarkle
- Organization
- github.com/flectar
- Location
- Spain
Our security engineering work
Flectar Mail: secure handling of untrusted content
Flectar Mail is our open-source native email client, developed in Rust.
Email clients process untrusted content received from external parties, making careful handling of message content, attachments, credentials, and network protocols particularly important.
Security-related design decisions include:
- Reduced attack surface: HTML email rendering uses a native Rust rendering pipeline rather than an embedded browser or WebView, and email scripts are not executed.
- Privacy protection: Remote images are blocked by default to help prevent tracking through externally loaded resources.
- Credential protection: Supported release platforms use secure credential-storage facilities, with production credential persistence designed to avoid plaintext fallbacks.
- Email encryption: Desktop OpenPGP/MIME signing and encryption are supported through GnuPG, with documented limitations.
- Release integrity: Published releases include SHA-256 checksums and GitHub build-provenance attestations.
Flectar Mail remains under active development. Its security architecture and implementation continue to be reviewed and improved.
- Source code: github.com/flectar/mail
- Security policy: SECURITY.md
- Releases: github.com/flectar/mail/releases
Cloudflare Turnstile for Flarum
Flectar also develops an open-source extension integrating Cloudflare Turnstile into the Flarum forum platform.
The extension provides configurable anti-abuse protection for registration, login, and password-recovery forms, helping administrators protect authentication-related workflows.
- Source code: github.com/flectar/flarum-ext-turnstile
Defensive security and vulnerability management
Our defensive security work concerns software and infrastructure that Flectar owns or is authorized to maintain.
Activities include secure code review, vulnerability identification, dependency-risk assessment, authentication and access-control review, controlled vulnerability reproduction, remediation development, and patch validation.
We also review security-related contributions to our open-source projects and coordinate with contributors and upstream maintainers when appropriate.
Responsible vulnerability disclosure
We welcome responsible security reports concerning Flectar-maintained software and services.
If you believe you have discovered a vulnerability, please contact:
Subject: Security vulnerability report
When possible, include:
- The affected product, version, or component.
- A description of the potential security impact.
- Reproduction steps using test accounts or sanitized data.
- Supporting technical evidence, such as relevant logs or a minimal proof of concept.
Please avoid publicly disclosing unpatched vulnerabilities before coordinated disclosure can take place. Do not send passwords, access tokens, private keys, or real users' confidential data.
Reports are reviewed by the maintainers, with remediation and disclosure coordinated as appropriate. Response times depend on availability and the complexity of the issue.
For Flectar Mail specifically, see our repository security policy.
Our commitment
Security is an ongoing engineering responsibility, not a one-time certification.
We aim to build systems with sensible security defaults, address identified weaknesses, and maintain clear channels for responsible disclosure. We continue to improve our security practices as our products and open-source projects evolve.