cargo-audit vs Grype
cargo-audit
rustsec.orgGrype
github.comSide by side
| Figure | cargo-audit | Grype |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Windows | — | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 2 |
| Spec score · Software Composition Analysis Software | 7.9 (#25) | 8.7 (#4) |
| Installation | Install it as a Cargo subcommand with `cargo install cargo-audit`. | Official binaries and source archives are provided for Linux, macOS and Windows, with installer-script, Docker and package-manager options. |
| License | The cargo-audit crates are licensed under either Apache License 2.0 or MIT, at the user's option. | The project is released under the Apache-2.0 License. |
| Purpose | Audits Cargo.lock files for crates with security vulnerabilities reported to the RustSec Advisory Database. | Grype scans container images, filesystems, and SBOMs for known vulnerabilities. |
Plans
In their own words
cargo-audit
cargo-audit has no write-up on Specifiction yet; its figures are above.
Grype
Grype is a free, Apache-2.0-licensed scanner for known vulnerabilities in container images, filesystems, and software bills of materials (SBOMs). It can also scan directories, individual files, archives, and packages identified by PURL or CPE. Coverage includes major operating-system package ecosystems and language packages such as Ruby, Java, JavaScript, Python, .NET, Go, PHP, and Rust; supported image formats include Docker, OCI, and Singularity. Grype uses EPSS, KEV, and risk scoring to help prioritize findings. OpenVEX can filter results or add context. Reports can be emitted as a table, JSON, SARIF, or a custom Go template. The project supports SBOM generation and runs on Linux, macOS, Windows, or in a self-hosted setup. Installation options include a Docker image and community packages such as Homebrew, MacPorts, Winget, Scoop, and Snapcraft. Individual package scanning is described as useful for lightweight vulnerability checks and compliance scanning of specific dependencies. Security updates are applied only to the most recent release, and vulnerability-report support is described as best effort.