Project URL and anon key
Both ship to the browser on purpose, and the scan locates them in your bundle and confirms which project they point at, the starting point for everything else.
Scan by stack
A React or Next.js app on Supabase carries its project URL and anon key in the browser by design, so your data’s safety rests entirely on Row Level Security being right. A free, read-only scan finds those keys in your shipped code and checks, on the app you submit, whether an anonymous caller can read what it shouldn’t.
Run a free scanBoth ship to the browser on purpose, and the scan locates them in your bundle and confirms which project they point at, the starting point for everything else.
The service_role key bypasses Row Level Security entirely. If one ever reached client code, that is a full-data-exposure incident, and the scan treats it as critical and pins it to the line.
On the app you submit, the scan checks whether the public anon key can read rows a visitor never should: the real-world symptom of RLS that is off or misconfigured.
With the anon key public by design, a table without a correct policy is readable by anyone who opens dev tools. The scan tells you which side of that wall your data is on.
AI-generated apps ship fast and often skip RLS. Recent disclosures found a meaningful share of such apps leaking data this exact way, so a one-minute scan is the cheapest way to know you are not one of them.
The free scan shows the exposed surface. Keygraph goes further and proves the exploit, so you fix what is actually reachable, not a checklist.
Supabase apps whose front end is built with React or Next.js. The scan checks for React or Next.js first, so an app on another framework is not scanned, even when it uses Supabase.
Yes, by design. The anon key is meant to live in the browser: it identifies your project and grants only what Row Level Security allows. The danger is a table with RLS off or a permissive policy, because then that public key reads everything in it.
Treat it as a breach. The service_role key bypasses Row Level Security entirely, so anyone who opens the browser's dev tools can read and write every table. Rotate it in the Supabase dashboard immediately, then find out how it reached the client bundle.
In the Supabase dashboard, each table under Authentication and Policies shows whether RLS is on and which policies apply. The scan checks the symptom from the outside: on the site you submit, it asks whether the public anon key can count rows in the tables your code names.
No. The exposure check requests a row count only, never row contents. It never signs in, never uses a privileged key and stores no table data. Its result is a yes or no per table. The same scan also covers the rest of the front end, and a Next.js app gets the Next.js specific checks.
Any React or Next.js app: every public script, the routes, APIs and exposed credentials it ships, pinned to file and line.
Exposed NEXT_PUBLIC_ keys, shipped source maps, and the route map an attacker rebuilds from your bundle.
Subdomains, DNS, email authentication and TLS posture, mapped from public sources only.
This free scan is a taste of Keygraph: continuous agentic pentesting that ships every finding with a working exploit.