Your auditor is on its way.
The download starts in a moment. If it does not, download it here. It is one read-only SQL file and a short README.
About a minute, nothing shared.
Open your own SQL editor
In your Supabase dashboard, open the SQL editor. Everything happens inside your project.
Paste the file and run it
It reads your database catalog only. It never reads your rows or changes a setting, and it even runs inside a read-only transaction.
Fix the criticals first
Findings come back worst first: the table, the hole, why it matters, and a starting-point fix to review before you run it.
Every finding comes with a fix. The pack writes them for you.
Each finding already carries a starting-point fix. The full security pack, $11.40 launch price Launch price USD 11.40 (normal USD 19) for the first 25 buyers or until 2026-10-31, whichever comes first. The code is already in the link., adds a tested recipe for every finding and for the three RLS errors people hit most, plus a Claude Code skill that writes the fixes for your exact tables.
Get the fix pack, $11.40 launch priceLaunch price USD 11.40 (normal USD 19) for the first 25 buyers or until 2026-10-31, whichever comes first. The code is already in the link.
Good. Run it again after every schema change.
New tables are where the holes come from, so the moment to rerun it is right after you add one. It checks the patterns that keep recurring in AI-built apps. It is not a full security review, and a high-stakes app still deserves one.
Two errors, answered in full.
42501: new row violates row-level security policy
The six causes, how to tell which one you hit, and the fix for each.
42P17: infinite recursion detected in policy
Why a policy can end up asking itself, and a tested way out.