Common issues in v0 apps
- Secret keys exposed through a NEXT_PUBLIC_ environment variable
- Server actions or route handlers that query Supabase with a service key and no ownership check
- Supabase tables without row-level security
- Missing security headers on the deployed site
Fixes you paste back into v0
Each finding comes with a fix prompt that names the file, the table and the change. Paste it into v0, redeploy, and use the free rescan within 14 days to confirm.
Before you scan
LeakScan supports apps with a Supabase backend and code on GitHub, served from a domain you control. Firebase, Neon, Replit-hosted apps and Bitbucket are not supported yet.
Common questions
Does LeakScan need access to my Vercel account?
No. It reads the GitHub repository, your Supabase catalog through a read-only role, and the live site as a visitor sees it.