Multi-tenant Postgres you can prove doesn't leak
Row level security is easy to switch on and easy to get subtly wrong. The mistakes pass your tests, because your tests go through the application, and the application isn't where the hole is.
npx slipstream-audit $DATABASE_URL · free and open source, coming to npm shortly
FORCE, not just ENABLE
Tables that enable row level security without forcing it, so the owner your app connects as skips every policy.
Policies that actually scope
Policies that never mention the tenant column, lack WITH CHECK, or are permissive enough to widen what a tenant sees.
No way around it
Connections as a superuser or a role with BYPASSRLS, which turn every policy off at once.