Checks · DB-008

DB-008 · Migrations not in repo

Why it matters

If the schema only lives in an admin screen, the next environment will not match production.

How we detect it

No Supabase or ORM migration directory.

How we fix it

Generate a baseline migration and commit it.

Can it be fixed automatically? With review

Related checks

• SEC-007 · Source maps public in production
• HDR-001 · Missing HSTS
• HDR-002 · Missing CSP
• HDR-003 · Clickjacking: no frame-ancestors or X-Frame-Options