Will It Vibe?Image pinned to the :latest tag
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
image: name:latest is a moving target: the digest behind it changes over time, so builds are not reproducible and a redeploy can silently pull different, untested code.
Why it matters
The :latest tag points at whatever the registry currently serves, so two deploys from the same compose file can run different image versions, and a redeploy can pull code that was never tested. This makes builds non-reproducible and incidents hard to trace back to a specific version. It also means an upstream change can break you without any change on your side.
How to fix it
Pin each image to a specific version tag (for example postgres:16.2), and for stronger guarantees pin to an immutable digest (name@sha256:...). Update versions deliberately through a normal change so you can test and roll back. Renovate or Dependabot can automate the version-bump pull requests.
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