We accept security reports for the latest code on the main and staging branches of this repository.
Please do not open a public GitHub issue for security vulnerabilities.
Report privately by emailing both:
Include:
- A short description of the issue and its impact
- Steps to reproduce (or a proof of concept)
- Affected component / version / commit if known
- Any suggested fix (optional)
We will acknowledge receipt within a few business days and follow up with next steps. Please give us reasonable time to investigate and release a fix before any public disclosure.
If GitHub private vulnerability reporting is enabled on this repository, you may also use Security → Advisories → Report a vulnerability.
- Never commit
.env, API keys, private keys, or cloud credentials. - Use
.env.exampleas the template for local configuration. - Seed / demo passwords (for example in Prisma seed data) are for local development only and must never be used in production.
- Rotate any credential that may have been exposed.
- Open pull requests against
staging, notmain. - Do not include real customer data, production hostnames with credentials, or live secrets in issues, PRs, or fixtures.