Find tables that are readable without RLS
Row level security is the difference between a private database and a public one. VibeSitter connects read-only, checks your public tables, and shows the exact SQL to turn RLS on and add a safe policy.
What you get
- ✓Detects public tables with row level security disabled.
- ✓Flags permissive policies and risky grants.
- ✓Shows a copy-paste SQL fix for each finding.
- ✓Includes a prompt you can paste into your AI tool.
Checks that matter here
RLS disabled on public tables
Finds tables in the public schema that anyone with the anon key could read or write.
Permissive policies
Flags policies that allow all rows or all operations when a narrower rule is expected.
Sensitive columns exposed
Highlights tables that commonly hold emails, tokens, or billing data when they are publicly readable.
Auth settings
Reviews signup, email confirmation, and password minimums that affect account safety.
Run a free check
Public URL only. No keys, no signup, no credit card.
Want database-level checks? See exactly what we access.
Common questions
Does VibeSitter read my table data?
No. The scanner runs metadata and configuration queries. It does not select rows or inspect customer PII.
What access does it need?
A read-only Supabase OAuth connection. We never ask for a service-role key or database password.