Supabase security scanner
One command, no install, no signup, and nothing leaves your machine. It reads your repository and tells you which tables are reachable and which keys are exposed, with the fix beside each finding.
npx github:humora2504/vibeproof .
What it checks
Database access
- Tables created without Row Level Security, read from your migration files
- Policies that pass for everyone, such as
using (true)granted toanon - Write privileges granted straight to the anonymous role
- Firebase and Firestore rules that say
allow read, write: if true - Storage buckets created public
Credentials
- Supabase
service_rolekeys, decoded from the token rather than guessed at - Stripe, OpenAI, Anthropic, AWS, Google, GitHub, Slack, SendGrid and Resend keys
- Secrets exposed through
NEXT_PUBLIC_,VITE_,EXPO_PUBLIC_and similar - Database connection strings carrying a password
- Env files that git is tracking
Application
- Admin database clients built in code that ships to the browser
- Endpoints and server actions that write without checking who is calling
- CORS wildcards combined with credentials, and authentication bypass flags left on
- Session secrets that are empty or too short, and SQL built by joining strings
What it deliberately does not flag
Your Supabase anon key. That key is meant to be public and ships in every frontend bundle by design. A scanner that shouts about it trains you to ignore scanners, which is worse than saying nothing. It checks whether Row Level Security is actually protecting you instead, because that is what decides what the anon key can reach.
What a finding looks like
CRITICAL Table "invoices" has no Row Level Security
supabase/migrations/001_init.sql:14
Supabase exposes every table in the public schema over a REST
endpoint. Without Row Level Security, anyone holding your anon
key, which ships in your frontend, can read and write this table.
Fix: alter table public.invoices enable row level security;
Every finding carries the reason and the fix. Evidence is redacted, so you can paste the output into an issue without leaking the key it just found.
As a gate on every pull request
- uses: humora2504/vibeproof@v1
with:
fail-on: high
Findings appear as annotations on the diff and the build fails. A key that cannot be merged cannot leak.
What it is not
It is not a security audit or a certification, and a clean result is not a promise that you are safe. It checks a specific, common and damaging set of mistakes. Anyone selling certainty at this price is selling something else.
It is MIT licensed with 29 tests, including a deliberately correct project that must produce zero findings. False positives are treated as bugs, because a scanner you learn to ignore protects nobody.
Fixing what it finds
Every finding prints its own fix, and for most projects that is enough. If you would rather have the policies generated for your own schema, with a script that creates two throwaway users and proves from outside that an anonymous visitor and the wrong logged-in user are both refused, that is the $19 Fix Pack. The scanner stays free either way.
Related
- "new row violates row-level security policy"
- Is my Supabase database public?
- NEXT_PUBLIC_SUPABASE_SERVICE_ROLE_KEY
- RLS Disabled in Public
- Supabase returns an empty array but the rows are there
- Is it safe to expose the Supabase anon key?
Check your own project
One command. No install, no signup, and it never touches the network. It reads your repository and tells you which tables are reachable and which keys are exposed, with the fix beside each finding.
npx github:humora2504/vibeproof .
Free and MIT licensed. If you want the policies generated for your own schema, and a script that proves an anonymous visitor is refused, there is a $19 Fix Pack. The scanner stays free either way.