| Version | Supported |
|---|---|
main on Sign.Page |
Yes |
| Other | No |
We recommend running the latest commit on main for self-hosted deployments.
Please do not open a public GitHub issue for security vulnerabilities.
Report security issues privately by opening a GitHub Security Advisory on this repository, or contact the maintainer via GitHub.
Include:
- A description of the issue and impact
- Steps to reproduce (if applicable)
- Your suggested fix or mitigation (optional)
We aim to acknowledge reports within a few business days and will coordinate disclosure once a fix is available.
- Keep
SUPABASE_SERVICE_ROLE_KEYserver-only; never prefix withNEXT_PUBLIC_. - Rotate Supabase keys if you suspect exposure.
- Review Supabase RLS whenever you customize
supabase/oss-schema.sqlor migrations.