Grype is an open-source, Apache-2.0-licensed command-line scanner that checks container images, filesystems, and SBOMsSBOMsA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. for known vulnerabilities across OS package ecosystems like Alpine, Debian, RHELRHELRed Hat Enterprise Linux, a commercially supported Linux distribution maintained by Red Hat, chosen by cyber tools for its long support lifecycle, certified hardware compatibility, and enterprise deployment prevalence., and Amazon Linux, as well as language ecosystems including Java, Python, Go, and Rust. It fits container-security and dependency-scanning work, aimed at application developers and platform teams who need vulnerability checks in a build pipeline rather than a full SBOMSBOMA software bill of materials, an inventory of the components and versions inside an application. It helps teams find affected software when a dependency has a vulnerability or licensing issue. or license-compliance suite, which the vendor covers with companion tools Syft and Grant under the same Anchore OSSOSSOpen-source software: code whose licence permits anyone to inspect, modify, and redistribute it. Cyber tools build on it to reuse auditable libraries without licensing fees. project. It supports VEXVEXA machine-readable statement from a vendor saying whether a CVE in a component actually affects their product. It is how a scanner is told to stop flagging a vulnerability that is not reachable. documents for suppressing known-unaffected findings and expiring ignore rules so waivers don't go stale. First committed in 2020, it has 173 contributors and a release 24 days ago, putting it among the more actively maintained tools in this space.
Grype is a vulnerability scanner for container images and filesystems.
Which of my container images or filesystems have known vulnerabilities right now?
scans installed OS and language packages against a vulnerability database and lists each match with the affected package, installed version, and severity
Which of these findings are actually exploitable in how I use the package?
checks any VEX documents supplied against the scan results and suppresses matches marked as not-affected, so waivers reflect real exceptions rather than blanket ignores
Have I silenced a vulnerability that's still unresolved months later?
supports ignore rules with expiration dates, so an old suppression stops applying and the finding reappears in the scan output once the date passes
Am I running a distro or package that's stopped receiving security fixes?
flags packages belonging to end-of-life distributions with a warning in the scan output, separate from the vulnerability matches themselves
Does this dependency's vulnerability actually apply to the version I have?
compares the installed version string against fixed-version data per ecosystem, including edge cases like APK version prefixes or RPM epoch fields, to avoid matching versions already patched
Can I check a Zarf package or an existing SBOM without rebuilding it into an image first?
reads the package archive or SBOM directly as a scan target and reports vulnerabilities without needing a running container or fresh build
51 capabilities
across 3 capability groups
· 2 backed by code, an API document or a real run
Built from Grype's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
+Enhanced package identification and matchingshippedImproves the accuracy of vulnerability detection by combining language-specific matching with CPE-based data-driven techniques.19 releases · first seen Apr 2021▸
Adds curated mapping of known CPEs to Grype package specifiers for improved match accuracy.
v0.111.0 · Apr 2026
· source
· release history
Adds Hex ecosystem matcher to detect vulnerabilities in Erlang and Elixir packages.
v0.107.0 · Jan 2026
· source
· release history
Supports hyphens in package version strings, enabling accurate matching for versions that include hyphens.
v0.103.0 · Nov 2025
· source
· release history
Uses AlmaLinux-specific advisories when scanning AlmaLinux systems for more accurate vulnerability matching.
v0.102.0 · Oct 2025
· source
· release history
Adds channel information to OS/distro detection for more precise distribution identification.
v0.97.0 · Jul 2025
· source
· release history
Adds package specifier overrides for kb, dpkg, and apkg package types, giving finer control over vulnerability matching.
v0.95.0 · Jul 2025
· source
· release history
+Distro Detection and SupportshippedProvides detection logic and vulnerability matching for specific operating systems and distributions including Echo OS, Raspbian, and RHEL EUS.12 releases · first seen Jun 2025▸
Adds SUSE Linux Enterprise Server (SLES) as a comprehensive distribution for vulnerability scanning.
v0.120.0 · Oct 2026
· source
· release history
Enables Fedora OS transformer so Fedora-based images are correctly matched against vulnerability data.
v0.109.0 · Feb 2026
· source
· release history
Supports more accurate vulnerability scanning for PostmarketOS distributions.
v0.108.0 · Feb 2026
· source
· release history
Adds SecureOS distro recognition for vulnerability scanning.
v0.107.0 · Jan 2026
· source
· release history
Adds support for Scientific Linux as a recognized distro.
v0.106.0 · Jan 2026
· source
· release history
Adds warnings when scanned packages belong to end-of-life distributions.
v0.106.0 · Jan 2026
· source
· release history
+Go vulnerability matchingshippedMatches vulnerabilities in Go packages using govulndb records, deduplicates against GHSA aliases, and ignores withdrawn advisories.11 releases · 1 other source · first seen Oct 2023▸
Deduplicates Go matches that are aliases of each other (same CVE reported under both a govulndb GO-* ID and its GHSA).
v0.116.0 · Jul 2026
· source
· release history
Emits vulnerabilities for golang.org/x/net packages sourced from govulndb, expanding Go ecosystem coverage.
v0.115.0 · Jun 2026
· source
· release history
Merges duplicate Go vulnerability matches with their corresponding GHSA matches to reduce noise in scan results.
v0.115.0 · Jun 2026
· source
· release history
Merges duplicate Go vuln matches with their corresponding GHSA matches to reduce noise in scan results.
v0.115.0 · Jun 2026
· source
· release history
Adds detection of golang.org/x/net vulnerabilities sourced from govulndb, expanding Go ecosystem coverage.
v0.115.0 · Jun 2026
· source
· release history
Respects withdrawn status of Go Vuln DB OSV records, reducing false-positive findings.
v0.114.0 · Jun 2026
· source
· release history
example
Scan a Go project image to surface golang.org/x/net CVEs now sourced directly from govulndb, with deduplication against GHSA entries.$ grype <your-go-image>:latest
v0.115.0 · Jun 2026
· source
+Improved Package IdentificationshippedEnhances vulnerability matching accuracy through distro-specific advisories, channel information, and hyphenated version support.8 releases · first seen Mar 2025▸
apk matcher does alias aware aggregation
v0.118.0 · Aug 2026
· source
· release history
Adds vulnerability matching on Hummingbird packages.
v0.111.0 · Apr 2026
· source
· release history
Strips the v prefix from APK versions for accurate version comparison during vulnerability matching.
v0.109.0 · Feb 2026
· source
· release history
New configurable behavior for how Grype handles missing dpkg/RPM epoch fields on incoming packages.
v0.106.0 · Jan 2026
· source
· release history
Supports hyphens in package version strings, enabling accurate matching for versions that include hyphens.
v0.103.0 · Nov 2025
· source
· release history
Uses AlmaLinux-specific advisories when scanning AlmaLinux systems for more accurate vulnerability matching.
v0.102.0 · Oct 2025
· source
· release history
+Ubuntu vulnerability matchingshippedMatches vulnerabilities against Ubuntu releases including Extended Security Maintenance channels and recently added distro codenames.6 releases · first seen Nov 2022▸
Adds Ubuntu ESM (Extended Security Maintenance) repository support for package matching
v0.116.0 · Jul 2026
· source
· release history
Adds Ubuntu 26.04 resolute to recognized distro codenames for accurate vulnerability matching.
v0.113.0 · Jun 2026
· source
· release history
Adds Ubuntu 26.04 resolute as a recognized distro codename for vulnerability matching.
v0.113.0 · Jun 2026
· source
· release history
Adds distro mapping and vulnerability scanning support for Azure Linux 3.0.
v0.81.0 · Sep 2024
· source
· release history
Adds Ubuntu as a supported Vulnerability Specification Source for detection coverage
v0.52.0 · Nov 2022
· source
· release history
+Unaffected Package TrackingshippedTracks explicitly unaffected packages and CPEs to automatically suppress false-positive vulnerability matches.4 releases · 1 other source · first seen Sep 2025▸
Adds include-matcher-suppressions config key (yaml: include-matcher-suppressions) to expose matches internally dropped by matchers — such as distro-fixed and built-in false-positive records — in the ignoredMatches output, making them visible when --show-suppressed is used.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
v0.119.0 · Sep 2026
· source
· release history
Extends ignore rules to cover owned sub-packages of distro packages, so a single ignore rule suppresses vulnerabilities across all related sub-packages.
v0.112.0 · May 2026
· source
· release history
Uses the unaffected match table to automatically remove vulnerability matches for packages confirmed unaffected, reducing false positives.
v0.100.0 · Sep 2025
· source
· release history
Adds unaffected package and CPE stores to the vulnerability database, enabling Grype to track which packages are explicitly marked as not affected.
v0.100.0 · Sep 2025
· source
· release history
example
Permanently enable suppressed-matcher match visibility in your Grype config so every scan includes distro-fixed dropped matches in its ignored output.$ include-matcher-suppressions: true show-suppressed: true
v0.119.0 · Sep 2026
· source
+Chainguard vulnerability matchingshippedIngests Chainguard vulnerability data and matches it against Chainguard packages during a scan.3 releases · first seen Nov 2024▸
Adds a Chainguard OSV transformer for processing Chainguard vulnerability data.
v0.116.0 · Jul 2026
· source
· release history
Adds the chainguard OSV transformer to ingest Chainguard vulnerability data
v0.116.0 · Jul 2026
· source
· release history
Supports scanning a single PURL directly from the CLI, enabling targeted vulnerability lookups without a full image or SBOM.
v0.84.0 · Nov 2024
· source
· release history
+Database Search Schema ExtensionsshippedAdds KEV, EPSS, fix availability, and CVSS metrics to the `grype db search` output for richer querying.3 releases · first seen Mar 2025▸
Adds fix availability information to the DB schema, surfacing whether a fix exists for matched vulnerabilities.
v0.99.0 · Aug 2025
· source
· release history
Adds KEV and EPSS fields to grype db search schema for richer vulnerability querying.
v0.88.0 · Mar 2025
· source
· release history
Adds CISA Known Exploited Vulnerabilities (KEV) information to the v6 vulnerability database.
v0.88.0 · Mar 2025
· source
· release history
+RHEL vulnerability matchingshippedExtends RHEL coverage by applying RHSA advisories across all applicable minor versions of RHEL.2 releases · first seen Jul 2025▸
Duplicates RHSA advisories across all applicable RHEL minor versions for more complete RHEL coverage.
v0.116.0 · Jul 2026
· source
· release history
Adds vulnerability matching support for RHEL Extended Update Support (EUS) streams.
v0.97.0 · Jul 2025
· source
· release history
+RPM source package filteringshippedPrevents false positives in CSAF VEX matching by correctly distinguishing binary RPM packages from source RPMs.2 releases · first seen Jun 2026▸
Supports source RPM filtering on the Hummingbird matcher.
v0.113.0 · Jun 2026
· source
· release history
Adds source RPM filtering for Hummingbird (CSAF VEX) matching, reducing false positives by distinguishing binary RPMs from source RPMs using an architecture qualifier.
v0.113.0 · Jun 2026
· source
· release history
+Database Search Filter EnhancementsshippedAdds fixed-state filtering and namespace emulation to `grype db search` for improved query precision and compatibility.2 releases · first seen Apr 2025▸
Adds fixed-state filtering to grype db search so practitioners can narrow vulnerability lookups to only fixed (or only unfixed) entries.
v0.101.0 · Oct 2025
· source
· release history
Adds v5 namespace emulation to db search output, improving compatibility when querying the vulnerability database.
v0.91.0 · Apr 2025
· source
· release history
+Direct PURL scanningshippedEnables targeted vulnerability lookups by accepting a single Package URL as input.1 release · 1 other source · first seen Aug 2024▸
Supports scanning a single PURL directly from the CLI, enabling targeted vulnerability lookups without a full image or SBOM.
v0.84.0 · Nov 2024
· source
· release history
example
Query the local Grype vulnerability database for details on a specific vulnerability without running a full scan.$ grype db info
v0.80.0 · Aug 2024
· source
+RPM package scanningshippedProvides the ability to review rpm packages for vulnerabilities, including support for newer versions using SQLite databases.2 releases · first seen Jun 2022▸
Grype gains the ability to review rpm packages for vulnerabilities.
v0.50.0 · Sep 2022
· source
· release history
Support newer versions of rpm that use Sqlite for the db instead of BerkeleyDB
v0.39.0 · Jun 2022
· source
· release history
+CPE-based matching for Rust cratesshippedEnables CPE-based vulnerability matching for Rust crates so that vulnerabilities only identifiable via CPE are not missed.1 other source · first seen Aug 2026▸
Enable CPE-based matching for Rust crates when scanning an image, so vulnerabilities reachable only via CPE (e.g. openssl rust-crate) are no longer silently missed.$ GRYPE_MATCH_RUST_USING_CPES=true grype alpine:latest
v0.117.0 · Aug 2026
· source
+Database consolidationshippedConsolidates the grype-db library directly into Grype to streamline database handling and management.1 release · first seen Feb 2026▸
Ports the grype-db library directly into Grype, consolidating database handling.
v0.109.0 · Feb 2026
· source
· release history
+Package Specifier OverridesshippedAllows finer control over vulnerability matching by overriding package specifiers for specific package types.1 release · first seen Jul 2025▸
Adds package specifier overrides for kb, dpkg, and apkg package types, giving finer control over vulnerability matching.
v0.95.0 · Jul 2025
· source
· release history
+Database Compatibility LayershippedProvides v5 namespace emulation in search output to improve compatibility with existing tooling querying the database.1 release · first seen Apr 2025▸
Adds v5 namespace emulation to db search output, improving compatibility when querying the vulnerability database.
v0.91.0 · Apr 2025
· source
· release history
+CPE-based vulnerability queryingshippedAllows requesting vulnerability data by a single CPE string via the `cpe:` input format.1 release · first seen Aug 2022▸
+Container image scanningverifiedScans a container image and reports any vulnerabilities found in its software components.22 releases · 13 other sources · first seen Aug 2020▸
Also counts toward: Command-line interface, JSON data export
release
22 total
Adds option to disable end-of-life (EOL) warnings in scan output.
v0.108.0 · Feb 2026
· source
· release history
Adds scanning support for MinimOS container images.
v0.93.0 · Jun 2025
· source
· release history
Adds EPSS (Exploit Prediction Scoring System) metrics to vulnerability scan results.
v0.92.0 · May 2025
· source
· release history
Adds indication of CISA Known Exploited Vulnerabilities (KEV) in scan output.
v0.92.0 · May 2025
· source
· release history
Exits with a distinct return code when a scan fails (as opposed to a scan that completes but finds vulnerabilities), enabling more precise CI/CD error handling.
v0.91.0 · Apr 2025
· source
· release history
Adds the database URL to the JSON descriptor block in scan output.
v0.90.0 · Mar 2025
· source
· release history
docs
Windows PowerShell redirection Windows PowerShell may write redirected output with UTF-16LE encoding. If another tool expects UTF-8 JSON, write the report with Grype’s --file option instead of > grype <image> -o json - -file ./ grype-report .json Last modified October 9, 2026: chore(deps): update tool versions (#298)…
seen Oct 2026
· source
Windows PowerShell redirection Windows PowerShell may write redirected output with UTF-16LE encoding. If another tool expects UTF-8 JSON, write the report with Grype’s --file option instead of > grype <image> -o json - -file ./ grype-report .json Last modified October 6, 2026: chore(deps): update tool versions (#296)…
seen Oct 2026
· source
Windows PowerShell redirection Windows PowerShell may write redirected output with UTF-16LE encoding. If another tool expects UTF-8 JSON, write the report with Grype’s --file option instead of > grype <image> -o json - -file ./ grype-report .json Last modified October 2, 2026: chore: reformat toml for…
seen Oct 2026
· source
Vulnerability scanner for container images, filesystems, and SBOMs supporting major OS and language package ecosystems.
we ran it
Grype reports it is running on linux/arm64, built with Go 1.26.5, and linked against Syft v1.50.0. The supported vulnerability database schema is version 6.
Aug 2026
· the full run
example
8 total
Scan a container image using a specific source with the new --from flag to control where Grype pulls the SBOM or image from.$ grype --from <source> <target>
v0.104.0 · Nov 2025
· source
Get a human-readable scan report instead of the default table output.$ grype <image> -o pretty
v0.88.0 · Mar 2025
· source
Scan a container and see colored severity levels directly in the terminal output$ grype quay.io/library/alpine:latest -o table
v0.73.0 · Nov 2023
· source
Scan a container image but ignore any vulnerabilities where the fix status is wont-fix or deferred$ grype --ignore-states wont-fix,deferred myimage:latest
v0.72.0 · Oct 2023
· source
Scan an image while applying OpenVEX documents to filter false positives or include exceptions.$ grype my-image:v1 --vex path/to/document.vex
v0.68.0 · Sep 2023
· source
Include a timestamp in the JSON report for correlating scan events with external logs or CI timestamps.$ grype ubuntu:20.04 -o json | jq '.timestamp'
v0.61.1 · Apr 2023
· source
+SBOM-based scanningshippedTakes an existing SBOM as input and scans it for vulnerabilities without re-cataloguing the software.5 releases · 6 other sources · first seen Nov 2020▸
Adds ProvideFromReader for in-memory SBOM processing without requiring a file on disk.
v0.111.0 · Apr 2026
· source
· release history
Adds import support for CycloneDX 1.4 SPDX and VEX artifacts to the scan input pipeline
v0.36.0 · Apr 2022
· source
· release history
Adds support for parsing CycloneDX format as SBOM input source
v0.34.1 · Mar 2022
· source
· release history
Adds support for reading SPDX SBOM documents as input sources
v0.33.0 · Feb 2022
· source
· release history
Add support for using an SBOM input document instead of invoking syft's cataloging functionality
v0.5.0 · Nov 2020
· source
· release history
example
Scan a CycloneDX 1.4 SBOM to generate a vulnerability report instead of scanning a filesystem or container directly.$ grype spdx:cyclonedx-1.4.json
v0.36.0 · Apr 2022
· source
Scan a CycloneDX SBOM file instead of a container image or filesystem.$ grype sbom:cyclonedx:bom.xml
v0.34.1 · Mar 2022
· source
Scan a container image by providing its pre-generated SBOM JSON file directly to Grype.$ grype --sbom syft-output.json
v0.5.0 · Nov 2020
· source
Pipe an SBOM into Grype$ cat ./sbom.json | grype
Scan a Syft SBOM file$ grype sbom:./sbom.json
Scan an existing SBOM$ grype sbom:./sbom.json
+Zarf package scanningshippedScans all SBOMs inside a Zarf package in one pass and traces each finding back to its source image.3 releases · 2 other sources · first seen Apr 2022▸
Adds zarf: scan target to scan all SBOMs within a Zarf package archive (.tar.zst), with per-finding provenance traced back to the originating image via package annotations.
v0.114.0 · Jun 2026
· source
· release history
Adds ability to scan Zarf packages for vulnerabilities.
v0.114.0 · Jun 2026
· source
· release history
Indicate the specific file or package location where a vulnerability was found
v0.35.0 · Apr 2022
· source
· release history
example
Scan a Zarf package archive for vulnerabilities across all bundled SBOMs in a single pass, with findings traceable to each source image.$ grype zarf:path/to/package.tar.zst -o json
v0.114.0 · Jun 2026
· source
Scan a Zarf package archive directly to find vulnerabilities before deployment.$ grype path/to/package.zst
v0.114.0 · Jun 2026
· source
+Risk score calculationdocumentedCalculates a composite risk score combining CVSS, EPSS, and other severity metrics into a single numeric value.4 other sources · first seen Oct 2026▸
Shared capability: Vulnerability prioritization
docs
- Calculated risk score combining CVSS, EPSS, and other severity metrics into a single numeric value (0.0 to 100.0) Last modified October 9, 2026: npm(deps-dev): bump cspell from 10.3.4 to 10.3.6 (#297) (464fe36)
seen Oct 2026
· source
- Calculated risk score combining CVSS, EPSS, and other severity metrics into a single numeric value (0.0 to 100.0) Last modified October 9, 2026: chore(deps): update tool versions (#298) (cc60c5a)
seen Oct 2026
· source
- Calculated risk score combining CVSS, EPSS, and other severity metrics into a single numeric value (0.0 to 100.0) Last modified October 6, 2026: chore(deps): update tool versions (#296) (6435297)
docs update · Oct 2026
· source
- Calculated risk score combining CVSS, EPSS, and other severity metrics into a single numeric value (0.0 to 100.0) Last modified October 2, 2026: chore: reformat toml for prettier-plugin-toml v3 (#294) (63701be)
seen Oct 2026
· source
+SSVC vulnerability prioritizationshippedStores NVD SSVC decision points and exposes them for use in vulnerability prioritization workflows.3 releases · first seen Dec 2022▸
Shared capability: Vulnerability prioritization
release
Stores NVD SSVC decision points in a new v6 decorator table, exposing GetSsvcs for richer vulnerability prioritization data.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
v0.120.0 · Oct 2026
· source
· release history
Stores National Vulnerability Database (NVD) SSVC decision points in the internal v6 decorator table, making prioritization data available for other outputs.
v0.120.0 · Oct 2026
· source
· release history
Reports the relevant CVE number alongside GHSA identifiers in vulnerability output.
v0.54.0 · Dec 2022
· source
· release history
+Other / not yet classified28 featuresFeatures we have not matched to a capability yet. A suggested match is marked.▸
+Package URL (PURL) type supportshippedsuggestedRepresents packages using Package URL types covering ecosystems including apk, alpm, deb, rpm, conan, vcpkg, portage, pub, and generic packages.1 release · 25 other sources · first seen Nov 2024▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Respects the rpmmod PURL qualifier, improving vulnerability matching precision for modular RPM packages.
v0.103.0 · Nov 2025
· source
· release history
docs
24 total
Package URL Type pkg:alpm Last modified October 9, 2026: npm(deps-dev): bump cspell from 10.3.4 to 10.3.6 (#297) (464fe36)
seen Oct 2026
· source
Package URL Type pkg:conan pkg:conan pkg:conan vcpkg-manifest-cataloger vcpkg.json pkg:vcpkg Complete Last modified October 9, 2026: npm(deps-dev): bump cspell from 10.3.4 to 10.3.6 (#297) (464fe36)
docs update · Oct 2026
· source
Package URL Type pkg:portage Last modified October 9, 2026: npm(deps-dev): bump cspell from 10.3.4 to 10.3.6 (#297) (464fe36)
docs update · Oct 2026
· source
Package URL Type pkg:pub pkg:pub Last modified October 9, 2026: npm(deps-dev): bump cspell from 10.3.4 to 10.3.6 (#297) (464fe36)
docs update · Oct 2026
· source
Package URL Type pkg:portage Last modified October 9, 2026: chore(deps): update tool versions (#298) (cc60c5a)
seen Oct 2026
· source
Package URL Type pkg:deb pkg:deb Last modified October 9, 2026: npm(deps-dev): bump cspell from 10.3.4 to 10.3.6 (#297) (464fe36)
seen Oct 2026
· source
example
Scan one specific package version for vulnerabilities using its PURL instead of an image or lockfile.$ grype 'pkg:pypi/requests@2.28.0'
v0.84.0 · Nov 2024
· source
+Vulnerability database managementshippedsuggestedProvides capabilities to inspect the status and update configuration of the local vulnerability database.16 releases · 4 other sources · first seen Dec 2021▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
Also counts toward: Command-line interface
release
16 total
Adds db diff command support for v6 vulnerability databases.
v0.111.0 · Apr 2026
· source
· release history
Supports importing the vulnerability database directly from a URL via grype db import.
v0.90.0 · Mar 2025
· source
· release history
Adds configuration for Maven Central rate limit handling.
v0.88.0 · Mar 2025
· source
· release history
Migrates database listing URL from https://toolbox-data.anchore.io/grype/databases/listing.json to https://grype.anchore.io/databases/v6/latest.json.
v0.88.0 · Mar 2025
· source
· release history
Replaces grype db diff with grype db search --modified-after and --published-after flags for filtering vulnerability changes.
v0.88.0 · Mar 2025
· source
· release history
Updates vulnerability matchers to use the v6 DB schema.
v0.88.0 · Mar 2025
· source
· release history
example
Import the Grype vulnerability DB directly from a remote URL instead of a local file — useful in air-gapped pipelines where you host the DB on an internal server.$ grype db import https://internal.example.com/grype-db.tar.gz
v0.90.0 · Mar 2025
· source
List all vulnerability DB providers Grype recognises to verify coverage before an air-gapped DB refresh.$ grype db providers
v0.83.0 · Oct 2024
· source
Fail the CI pipeline if Grype fails to update its vulnerability database.$ grype db update --db-check-fail-exit-code 1 || exit 1
v0.68.0 · Sep 2023
· source
Compare the installed vulnerability database against a remote source to see what has changed.$ grype db diff
v0.42.0 · Jul 2022
· source
+Custom output presentationshippedAllows users to define and apply custom formats for scan results via a presenter mechanism.12 releases · 3 other sources · first seen Apr 2021▸
release
12 total
Adds a built-in Markdown output template for report generation.
v0.102.0 · Oct 2025
· source
· release history
Improves the built-in HTML report template for richer vulnerability output.
v0.92.0 · May 2025
· source
· release history
New pretty output format option for human-friendly scan results.
v0.88.0 · Mar 2025
· source
· release history
Adds missing package information fields to SARIF report output.
v0.86.0 · Dec 2024
· source
· release history
Implements secondary sorting for default JSON output
v0.65.0 · Jul 2023
· source
· release history
example
Generate SARIF results for a CI system and JSON for downstream parsing in a single command.$ grype -o sarif=results.sarif -o json=results.json <image_name>
v0.64.0 · Jul 2023
· source
Generate an HTML report by specifying a custom template file during a scan.$ grype myimage --template /path/to/report.html.tmpl
v0.42.0 · Jul 2022
· source
Generate a SARIF report for CI/CD integration.$ grype --sarif my-app > results.sarif
v0.34.1 · Mar 2022
· source
+CycloneDX outputshippedsuggestedExports scan results as a CycloneDX document, including vulnerable version ranges to provide remediation context.9 releases · 1 other source · first seen Sep 2020▸
Suggested capability: Container image vulnerability scanning. This is our guess, not confirmed.
release
9 total
Adds a Locations column to the HTML report template to aid vulnerability triage.
v0.120.0 · Oct 2026
· source
· release history
Adds vulnerable version ranges to CycloneDX output format, giving richer remediation context in CycloneDX SBOMs.
v0.117.0 · Aug 2026
· source
· release history
Includes vulnerable ranges in cyclonedx output format
v0.117.0 · Aug 2026
· source
· release history
Adds CycloneDX output support for RpmMetadata, enriching CycloneDX SBOMs with RPM package details.
v0.101.0 · Oct 2025
· source
· release history
Adds EPSS score and KEV (Known Exploited Vulnerability) indications as vulnerabilities.ratings entries in CycloneDX report output.
v0.96.0 · Jul 2025
· source
· release history
Include Syft's cyclonedx component properties in Grype output
v0.55.0 · Jan 2023
· source
· release history
docs
Windows PowerShell redirection Windows PowerShell may write redirected output with UTF-16LE encoding. If another tool expects UTF-8 JSON, write the report with Grype’s --file option instead of > grype <image> -o json - -file ./ grype-report .json Last modified October 9, 2026: npm(deps-dev): bump cspell from 10.3.4 to…
seen Oct 2026
· source
+Test fixture regenerationverifiedRegenerates test fixtures from upstream vulnerability data, with options to preview changes, force updates, and fetch the latest schema.1 release · 7 other sources · first seen Mar 2022▸
release
artifacthub package index support added via the grype image for easier discovery and installation
v0.58.0 · Mar 2023
· source
· release history
command line
--root — name to use for the top-level struct (defaults to the schema title if empty)
v0.115.0 · Jun 2026
· command-line history
--pull — fetch the latest v1 schema from upstream and overwrite the pinned schema-v1.json before regenerating
v0.115.0 · Jun 2026
· command-line history
--dry-run — show what would be regenerated without making changes
v0.112.0 · May 2026
· command-line history
--fixture — path to a specific fixture to regenerate (optional)
v0.112.0 · May 2026
· command-line history
--vunnel-data — path to vunnel data directory (required)
v0.112.0 · May 2026
· command-line history
--force — regenerate even if fixture has been modified
v0.112.0 · May 2026
· command-line history
example
Specify the architecture/platform for the scan target.$ grype --platform linux/amd64 my-image
v0.34.1 · Mar 2022
· source
+Attestation-based scanningshippedEnables reading and validating attestation files to produce vulnerability reports from build provenance metadata.6 releases · 1 other source · first seen Apr 2022▸
release
Supports VEX documents when scanning directories and SBOMs, enabling VEX-based vulnerability suppression beyond just container images.
v0.101.0 · Oct 2025
· source
· release history
Adds VEX CSAF support for applying CSAF-format VEX documents to filter or contextualize scan results.
v0.99.0 · Aug 2025
· source
· release history
Adds KEV and EPSS fields to grype db search schema for richer vulnerability querying.
v0.88.0 · Mar 2025
· source
· release history
Adds CISA Known Exploited Vulnerabilities (KEV) information to the v6 vulnerability database.
v0.88.0 · Mar 2025
· source
· release history
Adds package name to VEX product identifiers, improving accuracy when applying VEX statements to matched vulnerabilities.
v0.87.0 · Jan 2025
· source
· release history
Enables reading attestation files, validating their integrity, and producing a vulnerability report from the attested metadata
v0.36.0 · Apr 2022
· source
· release history
example
Read and validate an attestation file to produce a vulnerability report based on the attested build provenance.$ grype attestation:attestation.json
v0.36.0 · Apr 2022
· source
+JavaScript package catalogingshippedAdds a cataloger to scan and identify JavaScript/Node.js dependencies from package.json files.6 releases · first seen Oct 2020▸
Also counts toward: Scripting language support
release
Adds support for scanning Gradle projects in Java dependency analysis.
v0.85.0 · Nov 2024
· source
· release history
Enable --http-timeout flag to control the duration for HTTP requests during SBOM generation
v0.75.0 · Apr 2024
· source
· release history
Adds dotnet detection engine to expand the list of supported ecosystems
v0.38.0 · May 2022
· source
· release history
Adds Dotnet support to detect .NET application components
v0.37.0 · May 2022
· source
· release history
Added parser for Pipfile.lock to cataloger (via Syft)
v0.17.0 · Aug 2021
· source
· release history
Adds package.json cataloger to scan JavaScript/Node.js dependencies
v0.2.0 · Oct 2020
· source
· release history
+Output Formatting EnhancementsshippedAdds a `pretty` output format and an improved HTML report template for human-readable results.5 releases · first seen Jul 2021▸
release
Adds a Locations column to the HTML template output to assist with finding affected files during triage.
v0.120.0 · Oct 2026
· source
· release history
HTML report template now includes Grype version and vulnerability DB version.
v0.111.0 · Apr 2026
· source
· release history
Improves the built-in HTML report template for richer vulnerability output.
v0.92.0 · May 2025
· source
· release history
New pretty output format option for human-friendly scan results.
v0.88.0 · Mar 2025
· source
· release history
Adds NVD CVSS scores to json output for matches on the vendor record
v0.15.0 · Jul 2021
· source
· release history
+VEX and CSAF IntegrationshippedsuggestedApplies VEX and CSAF documents to filter, contextualize, or suppress vulnerability findings.4 releases · first seen Aug 2025▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Adds CSAF VEX transformer for applying CSAF-format VEX documents to scan results.
v0.111.0 · Apr 2026
· source
· release history
Improves VEX product and subcomponent matching for more precise vulnerability exception handling.
v0.108.0 · Feb 2026
· source
· release history
Supports VEX documents when scanning directories and SBOMs, enabling VEX-based vulnerability suppression beyond just container images.
v0.101.0 · Oct 2025
· source
· release history
Adds VEX CSAF support for applying CSAF-format VEX documents to filter or contextualize scan results.
v0.99.0 · Aug 2025
· source
· release history
+Filesystem and directory scanningshippedScans a local filesystem or directory and reports vulnerabilities in the software packages it contains.1 release · 3 other sources · first seen Oct 2020▸
release
Adds path filtering for file system scanning
v0.28.0 · Dec 2021
· source
· release history
example
Scan a Node.js project directory for vulnerabilities using the new package.json cataloger.$ grype ./path/to/node/project
v0.2.0 · Oct 2020
· source
Scan the current directory$ grype dir:.
Scan a local directory for vulnerabilities$ grype ./my-project
+JSON output structure and key naming changesshippedChanges the JSON presenter root from a sequence to a mapping object and converts all keys from kebab-case to camelCase.4 releases · first seen Sep 2020▸
release
The JSON presenter output root is now an object (mapping) instead of an array (sequence), changing the top-level structure consumers parse.
v0.1.0-beta.10 · Sep 2020
· source
· release history
Changes the JSON presenter root from a sequence to a mapping object
v0.1.0-beta.10 · Sep 2020
· source
· release history
Changes all JSON output keys from kebab-case to camelCase (e.g., package-name becomes packageName)
v0.1.0-beta.8 · Sep 2020
· source
· release history
All JSON output keys are now camelCase; existing parsers expecting kebab-case will break.
v0.1.0-beta.8 · Sep 2020
· source
· release history
+Multi-architecture supportshippedAdds support for additional processor architectures including ARM32, s390x, and ppc64le.3 releases · first seen Jul 2022▸
release
Adds official support for the ppc64le architecture platform.
v0.54.0 · Dec 2022
· source
· release history
Add support for ARM32 (linux/armv7) architecture
v0.44.0 · Jul 2022
· source
· release history
+Shell completion supportshippedGenerates shell completion scripts for terminals to enable command auto-completion.2 releases · 1 other source · first seen Aug 2020▸
Also counts toward: Command-line interface
release
Adds shell completion support via the Cobra utility (--generate-shell-completion)
v0.1.0-beta.8 · Sep 2020
· source
· release history
Adds shell completion script generation via a new CLI command
v0.1.0-beta.5 · Aug 2020
· source
· release history
example
Generate shell completion for bash to enable auto-completion in your terminal.$ grype completion bash > /etc/bash_completion.d/grype
v0.1.0-beta.5 · Aug 2020
· source
+deb-get installation supportdocumentedSupports installation via deb-get as an additional distribution method.3 other sources▸
docs
deb-get deb-get install syft deb-get Syft package Last modified October 9, 2026: chore(deps): update tool versions (#298) (cc60c5a)
seen Oct 2026
· source
deb-get deb-get install syft deb-get Syft package Last modified October 9, 2026: npm(deps-dev): bump cspell from 10.3.4 to 10.3.6 (#297) (464fe36)
seen Oct 2026
· source
deb-get deb-get install syft deb-get Syft package Last modified October 6, 2026: chore(deps): update tool versions (#296) (6435297)
seen Oct 2026
· source
+Scan timing loggingshippedCaptures and logs the duration of scan operations for monitoring and reporting purposes.1 release · 1 other source · first seen Apr 2025▸
Capture scan duration by grepping the log for timing data after running a standard scan.$ grype --log-level info <image> | grep "timing"
v0.91.1 · Apr 2025
· source
+Configuration management and mergingshippedAllows inspecting, managing, and layering configuration files with named profiles.2 releases · first seen May 2024▸
Also counts toward: Command-line interface
release
Supports hierarchical merging of config files and named config profiles, letting teams layer shared and per-profile settings.
v0.83.0 · Oct 2024
· source
· release history
Adds grype config subcommand to inspect and manage Grype's configuration
v0.78.0 · May 2024
· source
· release history
+CI exit-code thresholdsshippedConfigures exit code values based on vulnerability severity counts to control CI pipeline success or failure.1 release · 1 other source · first seen Sep 2020▸
Also counts toward: CI/CD pipeline integration, Command-line interface
release
Adds --fail-on CLI flag to set exit-code thresholds based on vulnerability severity counts
v0.1.0-beta.9 · Sep 2020
· source
· release history
example
Fail a CI pipeline immediately if any critical vulnerabilities are found.$ grype --fail-on critical <image>
v0.1.0-beta.9 · Sep 2020
· source
+Machine-readable version outputshippedReturns the installed cyber tool version in a machine-parseable format for scripting and CI/CD workflows.1 release · 1 other source · first seen Sep 2020▸
Also counts toward: CI/CD pipeline integration, Command-line interface
release
Adds --json flag to the version subcommand to allow machine-readable version output
v0.1.0-beta.7 · Sep 2020
· source
· release history
example
Get the installed Grype version in a format suitable for scripting or CI logs$ grype version --json
v0.1.0-beta.7 · Sep 2020
· source
+End-of-life distro detectionshippedWarns when a scanned OS distribution has reached end-of-life, using available EOL or support-end dates from OS release information.1 release · first seen Oct 2026▸
release
Falls back to the SUPPORT_END date from OS release information when generating end-of-life warnings, so distros that publish a support-end date but no explicit EOL date are now flagged correctly.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
v0.121.0 · Oct 2026
· source
· release history
+Go symbol reachability analysisshippedsuggestedFilters out Go vulnerability findings for symbols that are not actually imported by the scanned binary, reducing false positives.1 release · first seen Jul 2026▸
Suggested capability: Static application security testing. This is our guess, not confirmed.
release
Adds lightweight Go symbol reachability analysis to suppress false positives for stdlib, golang.org/x, and third-party Go vulnerability advisories — only flags binaries that actually import the vulnerable symbols.
v0.116.0 · Jul 2026
· source
· release history
+Stale Suppression ManagementshippedSupports expiring suppressions to automatically re-surface ignored vulnerabilities after a set date.1 release · first seen Nov 2025▸
release
Supports expiring suppressions so ignored vulnerabilities are automatically re-surfaced after a set date, preventing stale waivers.
v0.104.0 · Nov 2025
· source
· release history
+Legacy database schema deprecationshippedRemoves support for DB v1 and v2 schemas, breaking setups relying on these legacy versions.1 release · first seen Dec 2024▸
release
DB v1 and v2 schemas are removed; any setup relying on these legacy database schema versions will break on upgrade.
v0.86.0 · Dec 2024
· source
· release history
+SARIF report field completenessshippedEnsures missing package information fields are included in SARIF output reports.1 release · first seen Dec 2024▸
release
Adds missing package information fields to SARIF report output.
v0.86.0 · Dec 2024
· source
· release history
+Gradle project scanningshippedAdds support for scanning Gradle-based Java projects during dependency analysis.1 release · first seen Nov 2024▸
release
Adds support for scanning Gradle projects in Java dependency analysis.
v0.85.0 · Nov 2024
· source
· release history
+WordPress plugin vulnerability detectionshippedsuggestedDetects vulnerabilities in WordPress plugins by analyzing their dependencies.1 release · first seen Oct 2024▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Adds WordPress plugin vulnerability detection support.
v0.82.0 · Oct 2024
· source
· release history
+Azure Linux supportshippedsuggestedProvides distro mapping and vulnerability scanning capabilities for Azure Linux 3.0.1 release · first seen Sep 2024▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Adds distro mapping and vulnerability scanning support for Azure Linux 3.0.
v0.81.0 · Sep 2024
· source
· release history
+Terminal user interfaceshippedProvides an interactive, text-based terminal interface for executing commands and managing scans.1 release · first seen Jul 2023▸
Also counts toward: Command-line interface
release
Ports the Grype UI to bubbletea for improved terminal interface handling
v0.64.1 · Jul 2023
· source
· release history
+Package list scanningshippedsuggestedAccepts a simple package list as input to scan specific packages without requiring a filesystem image or directory.1 release · first seen Aug 2022▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Accepts a simple package list as input (-p / --package-list) to scan specific packages without requiring a filesystem image or directory
v0.45.0 · Aug 2022
· source
· release history
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for Grype, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Grype puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Anchore's home, pricing and product pages and 24 more pages as they looked each month from September 2021 to October 2026: 64 renders, 7 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
Nothing first seen in this window. That doesn't mean Grype shipped nothing, only that we found no record of it.
Changes per month New Updated Retired
2026-10
4
How we count
Read from 10 of 116 release notes and docs updates we hold for Grype. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Grype's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
Show
Coverage in all entries
116 entries
No entries match these filters.
October 202611
September 20261
August 20262
July 20262
June 20266
May 20261
April 20261
February 20262
January 20263
November 20253
October 20252
September 20251
August 20253
July 20253
June 20252
May 20251
April 20252
March 20252
January 20251
December 20241
November 20242
October 20242
September 20241
August 20241
June 20241
May 20241
April 20242
November 20231
October 20232
September 20231
July 20233
June 20231
May 20231
April 20232
March 20232
January 20232
December 20221
November 20221
October 20221
September 20223
August 20222
July 20224
June 20222
May 20222
April 20222
March 20221
February 20221
December 20212
November 20211
October 20212
September 20213
August 20211
July 20211
June 20211
May 20211
April 20212
November 20201
October 20201
September 20204
August 20201
Project health
Issue, contributor and maintainer activity in anchore/grype, 2023-10 – 2026-09,
as of 2026-09-25. Twelve-month figures first; the trend lines run
the whole window.
Contributors42+3 vs prior 12 months
Maintainers4+3 joined · −2 left, last 12 months
Bus factor2committers behind half the commits
Community-filed99%of issues opened, last 12 months
Median time to close16 daysfirst maintainer reply 9.4 days
Open backlog330of 1,230 issues ever filed
Issues opened / month2 · 0communitymaintainers
Open backlog330
Contributors / month7
Commits / month9
Stars12,890
Issue themes, last 12 months
bugs 57%
features 22%
questions 1%
docs 0%
other 20%
Counts from the project's public repository and git history; no individuals
are identified. Maintainers are the committers covering 80% of the last year's
commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.
None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.