Build review credit-free preview

A static security review of a Supabase project: missing Row Level Security, policies that allow everyone, and missing write policies. Findings are explained in plain English with a fix you can paste into your editor. This preview never uses a review credit and never touches a live site. The full independent review is a separate step.

Your code never leaves your control. Your project is scanned the moment you upload it, and the files are discarded immediately afterward — nothing is stored, kept, or used to train anything.

Pick your project folder — the smallest thing that works is the folder that holds your .sql files (for a Supabase project, that's supabase/migrations; a whole project folder is fine too). We read .sql, .toml, .json, .example, and app source files (.js, .ts, .jsx, .tsx, .py) — everything else (including node_modules) is skipped in your browser and never uploaded. The scan runs, then your files are discarded.

Row Level Security is a Supabase check; other stacks are still scanned for secrets, dependency issues, and unfinished code.

Exclude paths (test fixtures, generated code)

Gitignore-style patterns, relative to the project root. A path listed here is skipped by every check and named in the scan's “what we scanned” manifest — nothing is hidden, and we only skip what you list (we never guess a path is a fixture). You can also ship a .bellerbuildignore file at your project root; we read it automatically.

What exactly does it need?

The scan looks at your database access rules, which live in your SQL migration files. That is almost always the supabase/migrations folder — the .sql files inside it are the whole point.

  • Smallest, fastest: select just supabase/migrations.
  • Also fine: select the whole project folder — we skip everything that isn't useful.
  • If your project is huge: still just pick the project root — we keep your .sql migration files first and trim the rest to fit the scan limit.

No Supabase project? The scan needs Supabase-style migration files; if yours are named differently, upload the folder that holds your .sql schema changes.

Scan a folder already on this server (advanced)

Only works for a path the server can reach. Uploaded scans are not monitored; a server-reachable path can be re-scanned by a monitoring subscription.

Ready. Choose your project folder to run the scan.