Will It Vibe?Image uses the latest tag
Part of Security, which counts for 30% 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
An image pinned to :latest is mutable, so the running code can change without a manifest change and cannot be reliably rolled back or audited.
Why it matters
An image pinned to :latest is a moving target. The tag can point at a different build tomorrow, so the same manifest can run different code across nodes and over time, and a rollback does not reliably return the previous version. It also makes incident forensics harder because you cannot tell exactly what ran.
How to fix it
Pin the image to a specific immutable reference: a version tag like 1.25.3 or, better, a digest like image@sha256:.... Wire your CI to update the pinned version deliberately rather than tracking latest. For third-party images, prefer digests so the content is fixed even if the tag is later reused.
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