Supabase Security Invoker View Drift Checker

Paste redacted Supabase view SQL, dashboard definition output, or migration diff notes and check whether a public view may have lost security_invoker = true, broad grants, or the regression evidence needed to prove RLS still applies.

Use this when

  • 1
    A view fronts protected rowsYour app reads through a public view that selects from RLS-protected tables.
  • 2
    A migration or dashboard edit changed the viewA create or replace view or diff may omit security_invoker.
  • 3
    Anon access must be provenYou need concrete anon/authenticated smoke tests before trusting the launch.
Use redacted SQL only. Do not paste secrets, private connection strings, real user data, customer records, payment data, private screenshots, full names, private handles, full transaction identifiers, credential values, service-role keys, or dashboard screenshots. This page runs locally in the browser and does not use network requests, browser storage, or a backend.

Ready.

View drift findings

Evidence to keep before launch

Need a second pass?

The fixed-scope report can review one redacted Supabase view/RLS packet: likely drift, grant boundary, anon/authenticated smoke tests, and the exact evidence to keep before users touch real data. The sample report is fictional and shows the report shape before checkout.

Source-backed problem set