Skip to main content
Security

Built to protect what you upload.

This page summarizes the security controls currently implemented in the product.

Implemented App Controls

The items below are materially present in the current codebase, compose stack, CI configuration, or user-facing security flows.

JWT cookie auth with revocation, single-session enforcement, issuer/audience/nbf validation, and HttpOnly cookie transport.
Role and ownership checks on protected resources, admin-only routes, and storage access paths.
Argon2id password hashing, account lockout, auth throttling, and reduced account-enumeration signals.
CSRF origin validation for unsafe cookie-authenticated requests plus strict CORS and trusted-host enforcement.
Upload MIME validation, quarantine flow, asynchronous ClamAV scanning, and malicious-file retention handling.
Generic client-safe errors with request correlation IDs and reduced filesystem/tool detail exposure.
Data minimization on file and bug-report APIs so storage paths and raw fingerprints are not exposed to users.
Secure response headers, cache suppression on sensitive auth flows, and hardened reverse-proxy topology.
CI security scanning with bandit, pip-audit, npm audit, semgrep, gitleaks, trivy, and Dependabot updates.
Report a vulnerability

Acknowledgement target: 3 business days.

fretpulse.engine@gmail.com
Disclosure policy
Access Governance
A documented role matrix covers user, moderator, and admin capabilities across the protected API surface.
Backend ownership and role guards enforce access to files, jobs, artifacts, storage, and administration; frontend role visibility is only a navigation aid.
Application request paths use ORM and parameterized statement access, with security reviews maintained alongside the implementation.