Will It Vibe?Deletion protection disabled
Part of Architecture & Best Practices, which counts for 15% 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
deletion_protection = false lets a single terraform destroy or console click permanently remove a database or load balancer, with no guard against accidents.
Why it matters
deletion_protection = false means a single terraform destroy, a mistaken console action, or a bad automation run can permanently delete the database or load balancer. For production resources that guard is worth keeping on, since the recovery cost of an accidental delete far outweighs the minor friction of turning protection off deliberately when you really do intend to remove it.
How to fix it
Set deletion_protection = true on production databases and load balancers. When you genuinely need to remove one, flip it to false in a dedicated change, apply, then destroy, so the deletion is always an explicit two-step action. Keep it enabled in the module defaults so new resources inherit it.
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