Will It Vibe?Multiple package-manager install layers
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
Two or more separate RUN layers each install system packages. Combining them into one RUN reduces image layers and lets a single apt/apk cache-clean apply. Heuristic.
Why it matters
Each RUN that installs system packages creates its own image layer, and separate installs cannot share a single cache-clean, so the image ends up larger and slower to build than needed. This is a heuristic about layering, not a correctness bug.
How to fix it
Combine the package installs into one RUN chained with &&, ending with the appropriate cleanup (rm -rf /var/lib/apt/lists/* for apt, --no-cache for apk). Keep the full set of packages the same.
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