Supabase security checks
RLS that is actually enforced, schemas that stay private, edge functions that check their callers. These are the rules lumioguard runs against a live Supabase project — connected read-only, rechecked on every scan.
Auth & service-role key safety
The key that bypasses RLS, and everywhere it reaches.
Auth hardening & exposure config
Project settings that widen the blast radius of a stolen credential.
Database DR & network
Whether you could recover, and who can connect.
Migration & schema safety
The migration that locks the table or loses the column.
Performance advisors
Supabase’s own lints, tied back to the code that triggers them.
Realtime & cost
Subscriptions and queries that bill by the row.
RLS & tenant isolation
Tables any logged-in user can read end to end.
Runtime error logs
What is actually failing in production right now.
Storage safety
Buckets and object URLs that are more public than intended.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.