supabase-drift-guard: a CI check for grant drift between your migrations and your live project

[SyrineSarray]

Built an open-source CI check that fails when live Supabase privileges drift from what your migrations define. For example, if a dashboard change accidentally gives anon access to a table. In my tests, supabase db diff didn’t catch that case.

Scope: Postgres grants only, including table, schema, and default privileges for anon / authenticated roles. It does not cover RLS, column-level grants, or function EXECUTE.

I’d love a few people to try:
npx supabase-drift-guard check .

on a real project and tell me whether the output looks right, noisy, or broken.

• Repo: https://github.com/SyrineSarray/supabase-drift-guard 
• Demo with a failing CI run: https://github.com/SyrineSarray/supabase-drift-guard-demo/actions/runs/36624907400