We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 4 since January 2026, each linked to its source.
grypeWhen scanning a Zarf package archive, run Grype with the `zarf:` target and JSON output to produce a vulnerability report. The documented example uses a `.tar.zst` archive.
grype zarf:<path/to/package.tar.zst> -o jsonWhen 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>When integrating Grype’s Go library and matching may need to stop early, call `FindMatchesContext` with a `context.Context`; it checks cancellation before each matcher call and returns on a context error.
ctx := context.Background() // replace with the workflow's cancellable context
remainingMatches, ignoredMatches, err := vulnMatcher.FindMatchesContext(ctx, pkgs, pkgContext)When scanning an image with Erlang or Elixir packages, run Grype to use its Hex matcher for GHSA data. To enable CPE matching for this ecosystem, set `match.hex.using-cpes` to `true`; it is `false` by default.
grype <image>