Please do not open a public GitHub issue for security bugs.
Email the maintainer (see the GitHub profile linked from this repo) with:
- A short description of the issue
- Steps to reproduce (or a PoC if safe to share)
- Impact assessment if you have one
You should get an acknowledgment within a few days.
- Never commit
.env,.env.local, or real API keys - Copy from
.env.example/landing/.env.exampleand fill locally or in Vercel/Supabase dashboards - Treat
SUPABASE_SERVICE_ROLE_KEYas server-only; it must not appear in client bundles
Public share URLs are intentional. Capsule snapshots are sanitized before upload; database access for shares relies on Supabase Row Level Security (see supabase/migrations/).