Analysis & detection
What is Container Scanning?
Inspecting container images for vulnerable OS packages, application dependencies and unsafe build practices.
A container image bundles a base OS layer, system packages and your application. Scanning walks each layer and reports known vulnerabilities, which most often live in the base image rather than anything your team wrote.
The practical output is usually a base-image upgrade recommendation. Tools differ in whether they can tell you which findings come from a layer you control versus one you inherited, a distinction that decides whether the report is actionable.
Top 12 Container Scanning tools
Every tool in the directory documented as supporting Container Scanning, 6 fully, 6 partially, with what its own documentation says.
Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.
- 1
Container image scanning included; Business plan only, scanner and scope not named.
- 2
15+ registries; base image vulns, layer secrets, malicious packages, misconfigurations
- 3Checkmarx OneCode Security Platform
Dedicated Container Security scanner for Dockerfiles and named images, plus private registry auth for DockerHub, ECR, GCR, GAR.
- 4CorgeaCode Security Platform
Base-image/OS/library CVEs across 7 named registries
- 5SnykCode Security Platform
Scans final image OS and app packages; base image upgrade advice; automatic Dockerfile fix PRs.
- 6
Container image/archive scanning across nine base OS families for vulns, misconfigurations, secrets
- 7
Dockerfile configuration checks and Kubernetes/Helm deployment validation; no container image vulnerability scanning
- 8
Trivy and Hadolint cover Dockerfiles in-repo; no container registry or image scanning described
- 9
Dockerfile analyzer flags root user, latest tags, missing health checks, exposed ports; no image or layer scanning.
- 10
Dependabot supports the docker ecosystem for updates; no container image vulnerability scanning documented
- 11
Dockerfile linting via Hadolint and Trivy misconfiguration checks; no container image vulnerability scanning
- 12
Dockerfile analysis only; no container image or layer scanning documented.
What to look for
- Whether findings are attributed to the layer that introduced them
- Registry integration for scanning images already deployed
- Base image upgrade recommendations rather than raw CVE lists
- Whether the scan runs in CI before push, or only on stored images
Related terms
FAQ
What is Container Scanning?
Inspecting container images for vulnerable OS packages, application dependencies and unsafe build practices.
How many tools support Container Scanning?
12 of the 20 tools tracked in this directory support Container Scanning, 6 fully and 6 partially, including Codacy, Aikido, Checkmarx One, Corgea, Snyk. Support is not the same as parity, since some implementations are narrower in scope, gated to a higher plan tier, or maintained only for existing customers. The note under each tool is what its own documentation describes.
What should you look for in Container Scanning?
Whether findings are attributed to the layer that introduced them. Registry integration for scanning images already deployed. Base image upgrade recommendations rather than raw CVE lists. Whether the scan runs in CI before push, or only on stored images.