Your AI Shipped the App. Did It Leave the Keys in the Repo?
Описание и применение
vibe-shipcheck — CLI‑инструмент, проверяющий конфигурацию Supabase‑приложений, созданных AI, и устраняющий ошибки, такие как отключённый RLS и коммит .env.
Задача
AI coding tools generate SQL migrations that leave row‑level security (RLS) disabled, exposing personal data in Supabase databases.
Результат
vibe-shipcheck identifies and fixes configuration gaps that AI-generated apps commonly miss, preventing accidental data exposure before deployment.
Рабочий процесс
- Install vibe-shipcheck via pip
- Run vibe-shipcheck against the project directory
- Review errors and warnings reported
- Apply suggested fixes (e.g., add ALTER TABLE ... ENABLE ROW LEVEL SECURITY, remove .env from git, restrict CORS origins)
- Re‑run vibe-shipcheck to confirm no errors
- Proceed to CI or deployment
Доказательства
AI coding tools write SQL migrations directly, and in that path Postgres row-level security defaults to off.
vibe-shipcheck 0.1.0 — pre-publish security check Scanning: /home/hao/my-app ERRORS: [env-committed] .env — .env file is tracked by git — its secrets ship with the repo fix: Add it to .gitignore, run git rm --cached .env, rotate every key it held.
[rls-disabled] supabase/migrations/001_init.sql — migration creates table(s) profiles without ENABLE ROW LEVEL SECURITY — readable by anyone with the anon key fix: Add ALTER TABLE <table> ENABLE ROW LEVEL SECURITY; plus policies for every table, or enable RLS in the dashboard.
- Дата записи: 2026-10-17T08:41:08.271Z