Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

Your AI Shipped the App. Did It Leave the Keys in the Repo?

说明与用途

vibe-shipcheck 是一个 CLI 工具,用于检查 AI 生成的 Supabase 应用程序的配置错误,例如禁用 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