supabase-sentinel

You can audit a Supabase project for RLS misconfigurations by running a targeted security audit that scans your working directory for policy vulnerabilities and unauthorized access risks. It reuses shared audit queries to detect misconfigured policies.

Supabase security vulnerabilities to check include RLS misconfigurations, permissive policies, and missing table-level protections. The audit checks for these vulnerabilities by applying anti-pattern detection and predefined audit queries to your Supabase project setup.

Yes, you can run a Supabase-only security audit without affecting existing triggers. This backward-compatible shim preserves the original audit surface, ensuring existing users experience no regression while auditing only Supabase components.

To fix Supabase RLS policies flagged during a security audit, you apply the provided fix templates to correct the misconfigurations. The audit workflow includes standardized templates to resolve detected policy vulnerabilities.

Yes, the Supabase security audit works with the standard database-sentinel workflow by dispatching to its shared assets. It reuses the workflow components, anti-patterns, audit queries, fix templates, and CI templates to deliver consistent audit results.