Will It Vibe?Deprecated top-level version field
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
The top-level version: key is obsolete under the Compose Specification and is ignored by modern Docker Compose. Keeping it can mislead readers about which schema is in force.
Why it matters
The top-level version: key is obsolete under the Compose Specification and is ignored by current Docker Compose, so it no longer controls schema behavior. Leaving it in place can mislead readers into thinking a specific schema version is being enforced when it is not. Removing it avoids confusion and matches current tooling.
How to fix it
Delete the top-level version: line. The Compose Specification infers the schema from the fields you use, so no replacement is needed. Confirm the file still validates afterward.
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