Will It Vibe?Taggable resource is missing tags
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A commonly-tagged resource (instance, database, volume, bucket, security group) declares no tags, which undermines cost allocation, ownership tracking, and tag-based access or automation policies. This is a hygiene heuristic and does not account for provider default_tags.
Why it matters
A resource that is commonly tagged (an instance, database, volume, bucket, or security group) with no tags is hard to attribute for cost, ownership, and lifecycle, and it cannot be targeted by tag-based access or automation policies. Consistent tagging is basic operational hygiene at any real scale. This is a heuristic and does not account for provider-level default_tags, so verify before acting.
How to fix it
Add a tags map with your standard keys (such as Environment, Owner, Project, and CostCenter). Prefer a provider default_tags block so every resource inherits the common set automatically, and add per-resource tags only for what is specific. Enforce required tags with a tagging policy or a pre-merge check.
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