Will It Vibe?DROP DATABASE statement present
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
DROP DATABASE removes the entire database, not just a table. This is common and often fine in a test/reset script, but its presence in a real migration file is worth a second look since running it against the wrong environment is unrecoverable without a backup.
Why it matters
DROP DATABASE removes the entire database, not a single table, and is common and often correct in a test/reset script. Its presence in what looks like a real migration file is worth a second look: running it against the wrong environment by mistake is unrecoverable without a backup, and there is no WHERE clause or partial-rollback path to limit the damage.
How to fix it
If this is a test/reset utility, keep it but make sure it is clearly separated from real migration files and, ideally, gated behind an explicit environment check. If it somehow ended up in a real migration path, remove it; dropping a live database is never something a migration runner should do automatically.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo