Menu

Extension Tables, Expo Configs, and Static MCP Scanners in supabase-rls-check 0.6.3
📰

Extension Tables, Expo Configs, and Static MCP Scanners in supabase-rls-check 0.6.3

DEV Community: postgres·Trung Thanh Tran·2 days ago
#u5oK7ukr
#devtopostgresql#devto#dev#supabase#extension
Reading 0:00
15s threshold

After shipping supabase-rls-check 0.6.0 on November 11, 2026, I ran into three edge cases across PostgreSQL system catalogs, React Native build files, and Model Context Protocol (MCP) directory scanners. Versions 0.6.1 through 0.6.3 address those three cases without adding network calls to the analyzer.

1. Extension-owned tables in public where ENABLE ROW LEVEL SECURITY fails

Rule rls_disabled flags tables in the public schema that have Row Level Security turned off, because PostgREST exposes the public schema to the anon and authenticated roles by default. For ordinary application tables, the remediation template in fix.sql suggests enabling RLS:

ALTER TABLE public . my_table ENABLE ROW LEVEL SECURITY ;

Enter fullscreen mode

Exit fullscreen mode

That remediation fails when a developer enables an extension such as PostGIS inside the public schema. PostGIS creates public.spatial_ref_sys owned by the bootstrap superuser ( supabase_admin ).…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.