Supabase RLS and policies
Find tables without Row Level Security, API grants on unprotected tables, missing applicable policies, and policies that allow every row.
Run a read-only scan for unsafe RLS policies, exposed database tables, and public Supabase Storage buckets. See the findings immediately and get a report by email.
The Supabase scanner reviews Postgres and Storage metadata for access-control mistakes. It uses fixed checks, reports the evidence, and leaves your application data untouched.
Find tables without Row Level Security, API grants on unprotected tables, missing applicable policies, and policies that allow every row.
Identify public Storage buckets whose objects can be served without an authenticated download request.
Inspect catalogue metadata through a server-owned read-only query—never application rows, generated SQL, migrations, or settings.
Connect through Supabase OAuth, choose a project, and Defencecore runs fixed, read-only catalogue checks. It then shows the findings in your browser and emails the same report.
No. Defencecore uses read-only Supabase OAuth and never asks for a service-role key, database password, personal access token, or SQL from your browser.
The scan checks for tables without Row Level Security, exposed API grants, missing or unsafe policies, unconditional policy expressions, and public Supabase Storage buckets.
No. The scanner inspects Postgres catalogue and Storage metadata using a server-owned read-only query. It does not select application rows or write migrations, policies, or settings.