supabase-audit-buckets-read

You need an anon or service role key to authenticate with your Supabase project. The audit uses these keys to access all reachable buckets and validate their access controls and data exposure levels.

The audit identifies files that may contain credentials or secrets exposed to the public by testing read access, metadata visibility, and public URL accessibility across all reachable Supabase storage buckets.

Yes, the audit validates bucket access methods using either anon or authenticated keys to detect public exposure and verify RLS-compliant restrictions across all reachable Supabase storage buckets.

The audit enforces progressive context updates and logs each finding to export structured evidence for remediation, generating traceable evidence directories and progress logs for security audits.

Run an audit that lists all reachable buckets, enumerates files, and validates access methods to detect public exposure and confirm RLS-compliant restrictions across your Supabase storage environment.