IPCRIME Underground Atlas — an independent, source-grounded editorial reference. Last reviewed November 20, 2026. This is not a live investigative finding.
A dependency scanner measures known advisory matches against a snapshot of software, not exploitability in every product.
Side-by-side capability matrix
| Product / approach | Type | Strength | Caution |
|---|---|---|---|
| Trivy | Container, IaC and dependency scanner | Broad development-platform coverage | Scope and data freshness require configuration |
| Grype | Image and filesystem vulnerability analyzer | Package inventory and matching workflows | Accuracy depends on available package metadata |
| OSV-Scanner | Open vulnerability database ecosystem | Package and lockfile advisory correlation | Not a replacement for runtime and configuration controls |
How to evaluate fairly
- Record scanner version, data feed date and the exact artifact scanned.
- Investigate false positives, backported fixes and opaque vendored dependencies.
- Combine with SBOM and vendor remediation documentation.
Choosing for your environment
Test each tool on the same fixed software artifact and audit a representative sample of matches before comparing counts.
Method and limitations
This is a research comparison, not an IPCRIME hands-on benchmark. Features, licensing and vendor claims may change; tests must state product versions, environment, workload and date. No paid editorial ranking or universal winner is asserted.
Official documentation and independent evaluation sources
Source: trivy.dev. Recorded by IPCRIME on November 20, 2026; verify updates against the original source.
Source: github.com. Recorded by IPCRIME on November 20, 2026; verify updates against the original source.
Source: google.github.io. Recorded by IPCRIME on November 20, 2026; verify updates against the original source.