CodanopySecurity scanning for AI-generated apps
For Supabase

Security scanning for Supabase apps

In a Supabase app the browser queries your database directly with the public anon key, so row level security policies are the whole authorization layer. One missing or over-broad policy and any visitor can read or change data.

Codanopy detects Supabase from @supabase/supabase-js, @supabase/ssr, or the Python supabase package and runs Supabase-specific checks on top of its dependency, secret, and pattern scans: it reads the row level security policies in your SQL migrations, and tells a public anon or publishable key apart from a service_role or sb_secret_ key that must never leave the server.

What to watch for

  • A table created in a supabase/ migration that never enables row level security — Supabase serves public tables over its API, so anyone holding the anon key from your frontend can read and write it
  • An update, delete, or catch-all policy written as using (true), a common shortcut for making a permission error go away that lets every visitor change every row
  • The service_role key stored under a VITE_, NEXT_PUBLIC_, or EXPO_PUBLIC_ variable, which the bundler inlines into the browser bundle — and that key skips every policy
  • A security definer function in the public schema, callable by anyone through /rpc and running with its owner's rights instead of the caller's

Run a free scan on the homepage — $49 unlocks the explanation and fix prompt for every finding. See how the scan works or why AI-generated code carries different risk.

Codanopy is not affiliated with Supabase.