Image has no explicit tag
Part of Security, which counts for 30% 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
An image reference with no tag resolves to :latest, which is mutable and non-reproducible. Digest-pinned or version-tagged images are excluded.
Why it matters
An image reference with no tag resolves to :latest, with the same mutability and reproducibility problems as pinning to latest explicitly: the running code can change without a manifest change and cannot be reliably rolled back. This check only flags references with no tag at all; digest-pinned and version-tagged images are excluded, and it is a heuristic.
How to fix it
Add an explicit immutable reference to each untagged image, a version tag such as 1.25.3 or a digest such as image@sha256:.... Confirm the tag you add matches what is currently deployed so behavior does not change unexpectedly. Update pins deliberately through CI rather than leaving images untagged.
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