Build fetches content over cleartext http://
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
A RUN downloads with curl/wget over http://, so the response is unauthenticated and can be modified in transit before it lands in the image.
Why it matters
Fetching with curl or wget over http:// pulls content over an unauthenticated, cleartext connection, so anyone on the network path can read or modify the response before it is written into your image. That is a supply-chain tampering risk during the build.
How to fix it
Switch the URL to https:// and keep certificate verification on. Prefer a pinned, versioned artifact and verify it against a checksum after download. If the source has no https endpoint, mirror the artifact somewhere you control that does.
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