Grype vs Sandworm Audit
Grype
github.com
Sandworm Audit
sandworm.devSide by side
| Figure | Grype | Sandworm Audit |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | Yes | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| Self-hosted | Yes | — |
| Plans published | 2 | 1 |
| Spec score · Software Composition Analysis Software | 8.7 (#4) | 7.2 (#52) |
| Intended users | The project documentation describes individual package scanning as useful for lightweight vulnerability checks and compliance scanning of specific dependencies. | The homepage describes it for auditing JavaScript and PHP dependencies, with CLI use in terminal, CI, and Git hook workflows. |
| Purpose | Grype scans container images, filesystems, and SBOMs for known vulnerabilities. | Sandworm Audit scans a project and its dependencies for vulnerabilities, license issues, and metadata issues. |
| Support | Commercial support is offered through Anchore, while community help is routed through issues, contribution documentation and community meetings. | The documentation directs support questions and feature requests to GitHub discussions and bug reports to GitHub issues. |
Plans
In their own words
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.
Sandworm Audit
Sandworm Audit has no write-up on Specifiction yet; its figures are above.