Supabase · Firebase · Next.js

Scan your Supabase project for exposed tables and keys.

One command, no install, nothing leaves your machine. It reads your migrations and your source, and reports the tables anyone can reach and the keys anyone can see, with the fix beside each finding. Free and open source.

npx github:humora2504/vibeproof .
npx github:humora2504/vibeproof
  vibeproof  v1.0.0
  184 files - Supabase, Next.js - 61ms

   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;

   CRITICAL   Supabase service_role key is in code that ships to the browser
      .env.local:3  -> eyJhbG...Q1Ng (218 chars)
      The service_role key bypasses Row Level Security completely.
      Fix: Rotate it in the dashboard, then use it only in server code.

  Summary: 7 critical - 4 high - 2 medium

The scanner is free and open source, for ever. The Fix Pack is a one-off $19. No account, no subscription.

This is not a hypothetical

98% of 1,072 AI-built apps scanned had security flaws. 172 allowed unauthenticated deletes. Symbiotic Security, June 2026
88% of 50 audited apps had Row Level Security disabled. 78% leaked secrets in the repository. Independent audit, May 2026
7% of 1,764 Lovable and Bolt apps shipped with a wide-open database. Survey, 2026

These are other people's numbers, not ours. We have sold nothing yet and have no customers to quote, so there are no testimonials on this page.

Start with the free scan

One command, no install, no signup, nothing leaves your machine. It reads your repository and tells you what is exposed, with the fix next to each finding.

npx github:humora2504/vibeproof .

It runs offline, sends nothing anywhere, and prints redacted evidence so you can paste the output somewhere without leaking the key it just found. Read the source.

Then fix it, and prove you fixed it

Finding the holes is the easy half. The hard half is writing correct policies for every table, remembering that table privileges are checked before policies are, and then knowing it worked rather than hoping. The dashboard showing a green shield is not proof.

The Fix Pack reads your migrations, works out who owns each row, and writes:

rls_policies.sql

Policies for every table, matched to your ownership columns: user-owned, organisation-owned via a membership table found in your own schema, or self-owned by a key referencing auth.users. Enables and forces Row Level Security and revokes the table privileges from anon that people forget. Your existing policies are left in place and listed for review, because a policy you wrote deliberately is not ours to delete. One transaction.

rls_tests.mjs

It creates two throwaway users, writes a row for one, and then checks from outside that an anonymous visitor is refused, that the other user cannot read, change or delete that row, and that the owner still can. Then it deletes the test users.

REPORT.md

Every table, whether Row Level Security is on today, which column it assumed is the owner and how confident it is. Tables where no owner could be identified are set to deny everything and listed for you to decide, because a table that errors is safer than one that leaks.

ci.yml + 4 playbooks

A GitHub Actions gate that fails the build on a critical or high finding, so this cannot regress. Plus runbooks for rotating a leaked key in the right order, locking down storage, hardening server actions, and what to do in the first hour after a leak.

What the proof looks like

node rls_tests.mjs
  vibeproof :: Row Level Security proof
  two test users created

  table: invoices
    PASS  invoices: anonymous read is blocked
    PASS  invoices: anonymous insert is blocked
    PASS  invoices: another user cannot read this user's rows
    PASS  invoices: another user cannot modify this user's row
    PASS  invoices: another user cannot delete this user's row
    PASS  invoices: the owner can still read their own row

  30 passed, 0 failed
  Every table above denied the anonymous visitor and the wrong user.

Before you apply the policies, that output is red. That contrast is the whole product.

See the real output before you pay. There are no customers yet, so there is no case study to show you. Instead the full output of the paid generator, run over a representative nine-table multi-tenant schema, is published in the open: the schema, the report, the SQL and the proof script. Judge it before deciding.

How it works

  1. Pay $19 once Stripe's own checkout. Card details never touch this site.
  2. Download the pack Stripe sends you straight to the download page, which unlocks the pack in your browser. Measured at 1.9 seconds on desktop and 1.3 on mobile, with no server involved. Nothing is sent by email, so nothing gets lost in spam.
  3. Run it on your project node vibeproof-fix.js . It reads your migrations and writes the five files into a folder. Takes a second.
  4. Read the SQL, then apply it To a branch or a copy first. It is plain SQL with comments, not a black box.
  5. Run the proof node rls_tests.mjs. Green means an anonymous visitor and the wrong user were refused, checked from outside your app.

Nothing in that chain needs a server or a person, so it works at any hour. Total time from payment to a proven lockdown: about fifteen minutes on a normal project.

$19one-off, not a subscription

Works on any project with SQL migrations. Generates policies for as many tables as you have, on as many projects as you own. Yours to keep, including the generator.

Buy the Fix Pack — $19 Secure checkout by Stripe

If it does not do what this page says it does, reply to your Stripe receipt within 30 days and you get your money back. No form to fill in.

Why not just use the free checklist

Rather than compare against products we have not tested, here is exactly what is included and what is not:

What you getFree scannerFix Pack, $19
Finds tables without Row Level Security, permissive policies, exposed keysyesyes
Runs offline, sends nothing anywhereyesyes
Gate on every pull requestyesyes
Policies generated for your own schemanoyes
Script that proves anon and the wrong user are refusednoyes
Rotation, storage and incident playbooksnoyes

If your project has three tables and you are comfortable writing policies, the free scanner is genuinely all you need. Take it, it costs nothing. The pack is for the case where you have twenty tables, a launch this week, and no appetite for finding out later which one you missed.

Questions

Does anything leave my machine?

No. The scanner and the generator both run locally and make no network requests. You can read the source of the scanner before you run it. Findings print redacted evidence, so a key it finds is never echoed in full.

Will it break my app?

It can, and that is deliberate for one case. Turning on Row Level Security denies everything until a policy allows it, so a table that was silently world-readable will start returning nothing until the right policy is in place. That is the point.

The generated SQL is a single transaction with comments, meant to be read before it is run, and the report tells you which tables it was unsure about. Apply it to a branch or a copy first. Tables where no owner column could be found are set to deny everything and listed for your decision rather than guessed at.

What if it cannot find my schema?

It reads SQL migrations from the usual places: supabase/migrations, migrations, db/migrations, prisma/migrations, drizzle, sql and database. If your schema only exists in the Supabase dashboard, export it first with supabase db dump --schema public -f supabase/migrations/000_schema.sql and run it again. If that still does not work, ask for a refund.

Is this a security certification?

No, and anyone selling you one for $19 is lying. It checks a specific, common and damaging set of mistakes: access to your tables and your storage. It does not review your application logic, your dependencies, or your infrastructure, and a clean result is not a guarantee that you are secure.

Firebase, Prisma, Drizzle, other databases?

The free scanner checks Firebase rules, Firestore and Realtime Database, alongside Supabase and Postgres. The Fix Pack generates Postgres Row Level Security, so it applies to Supabase and to any Postgres database. Prisma and Drizzle projects work as long as their SQL migrations are in the repository. If you use Firebase only, the free scanner is the useful half and the pack is not for you.

Who made this?

One developer, working in the open. The scanner's source is on GitHub, including its test suite. There are no customer testimonials on this page because there are no customers yet. When there are, they will be real ones.

Row Level Security broke my app. Is that this tool's fault?

Turning it on denies access until a policy allows it, so a table that was silently world-readable stops returning rows until the right policy exists. That is the protection working, not a fault. The error you will see is new row violates row-level security policy, and that page explains the four causes in the order worth checking.

How do I get a refund?

Reply to the Stripe receipt that lands in your inbox and say it did not work. Within 30 days, no questions and no form. Stripe handles the refund itself.


Guides

Written for the moment you are actually in, with the fix rather than the theory.

Run the free scan first

Take the free half whether or not you ever buy anything. If it comes back clean, you have lost thirty seconds. If it does not, you have found out from a terminal rather than from a stranger.

npx github:humora2504/vibeproof .