grype db diff compares Grype v6 databases by package impact
Introduced 2026-04-09 · score 0.97
HOW TO USE IT
When you need to identify package matching changes between two Grype v6 databases, run `grype db diff <old_db_url_or_path> <new_db_url_or_path>`; it reports packages with added, removed, and modified vulnerability matches.
grype db diff <old_db_url_or_path> <new_db_url_or_path>WHY THIS HELPS
Compare two Grype v6 databases to identify vulnerability data changes that affect package matching.
REQUIREMENTS AND LIMITATIONS
- Version: v0.111.0
- old_db_url_or_path (required): First database: HTTP(S) URL, directory containing `vulnerability.db`, `.db` file path, or supported DB archive path.
- new_db_url_or_path (required): Second database; same supported URL or path forms as the first database.
- --output, -o: Output format; available formats are `text` and `json`.
- Prerequisite: Use Grype v0.111.0 or later with Grype v6 databases.
- The command compares Grype v6 databases.
- Docs conflict: The v0.111.0 source command syntax permits one or two positional database arguments, while the release note describes comparing two databases. The usage here follows the card's two-database task.
FIRST-PARTY EVIDENCE
- https://github.com/anchore/grype/releases/tag/v0.111.0
- https://github.com/anchore/grype/pull/3277
- https://raw.githubusercontent.com/anchore/grype/v0.111.0/cmd/grype/cli/commands/db_diff.go
- https://raw.githubusercontent.com/anchore/grype/v0.111.0/grype/db/v6/diff/db_resolver.go
Check the installed version and the source before using it. Entry JSON