1
Proposal: SlowQL static analysis of migration scripts - insights and recommendations
Source: supabase/supabase#45110 · opened by @makroumi
Hi Supabase team, I hope you're doing well. I ran a static analysis of all your migration scripts (supabase/migrations/*.sql) using SlowQL an offline SQL analyzer I maintain with 282 rules covering security, reliability, quality, performance, cost, and compliance. This is not a list of bugs or a criticism of your code. These are insights and observations. Many of the patterns flagged are likely intentional given Supabase’s architecture, RLS requirements, migration strategies, and specific workflows. I’ve tried to surface things that might be worth reviewing or could be improved in the long term, but context is everything. <img width="3432" height="4013" alt="Image" src=" /> Summary of the analysis: • 40 migration files scanned • 34 files with issues (6 clean) • 317 total issues across 32 unique rules The most common category is Quality (226 issues), followed by Reliability (53). There are also 31 critical + high sev…
No pledges yet. Be the first to back this.
Comments
Similar requests
Improvements to the SQL Editor
1 vote · 0 comments
Supabase migrations don't include table/column comments
3 votes · 0 comments
Restrict database schema changes in web UI
13 votes · 0 comments
Missing features for using management API in CI
1 vote · 0 comments
Rollback ("down") Migrations
171 votes · 0 comments
No comments yet.