Grype vs ts-scan
Grype
github.comts-scan
trustsource.ioSide by side
| Figure | Grype | ts-scan |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | Yes | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 2 | 0 |
| Spec score · Software Composition Analysis Software | 8.7 (#4) | 7.3 (#49) |
| CI/CD integration | Grype can run directly in build pipelines or through Anchore's Container Scan GitHub Action, with pipelines able to fail on severity thresholds. | The maker says ts-scan integrates into GitHub workflows as a GitHub Action. |
| Headquarters | Santa Barbara, California, United States | Frankfurt am Main, Germany |
| Installation | Official binaries and source archives are provided for Linux, macOS and Windows, with installer-script, Docker and package-manager options. | The maker documents installation with pip and says Docker images and source builds are available in the repository. |
| Intended users | The project documentation describes individual package scanning as useful for lightweight vulnerability checks and compliance scanning of specific dependencies. | The maker describes ts-scan as an open-source CLI scanner for use in CI/CD pipelines to identify dependencies and create SBOMs. |
| License | The project is released under the Apache-2.0 License. | The repository identifies ts-scan as Python software under the Apache-2.0 license. |
| Purpose | Grype scans container images, filesystems, and SBOMs for known vulnerabilities. | ts-scan scans software dependencies and generates a software bill of materials (SBOM). |
| SBOM formats | Grype accepts Syft JSON, SPDX JSON/XML/tag-value and CycloneDX JSON/XML SBOMs. | It exports SBOMs in SPDX and CycloneDX formats. |
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.