Grype (Anchore)
About Grype (Anchore)
Grype's product generates SBOMs at every commit, build, and deployment, capturing dependencies, file metadata, licenses, and content. It scans SBOMs continuously for vulnerabilities, secrets, and malware. It adds compliance checks to build pipelines to ensure runtime environments meet formal requirements.
Used for
- Establishing DORA, CRA, and NIS2 compliance with automated SBOM and vulnerability workflows.
- Searching for malware signatures in container images and blocking deployment to production.
- Identifying unencrypted secrets within files in container images.
- Sending security or compliance finding alerts to developers in their native tooling.
Who it is for
- Small teams or business units seeking a prescriptive deployment.
- Centralized platform or security teams building scale-out environments.
From Grype (Anchore)'s own website, read 2026-10-23. How we build listings.
How to evaluate Application Security
This is how the CIOPages Research Team evaluates this category. It is not an assessment of Grype (Anchore). It comes from our DevSecOps & Application Security Testing buyer guide.
Other Application Security Vendors
View allCIOPages put this listing together from public sources. It’s information, not an endorsement. How we build listings. Work here? Claim this listing or .
Quick Facts
anchore.com Pricing pageWe publish a detail only when we can point at the page it came from. Know when Grype (Anchore) was founded or where it is based? Send it to us, free.
Explore
Keep reading
Estimate the avoided breach cost to make security spend more concrete and defensible.
Assess API program maturity across design, security, documentation, and lifecycle.