cargo-deny vs ScanCode.io
cargo-deny
embarkstudios.github.ioScanCode.io
scancode.ioSide by side
| Figure | cargo-deny | ScanCode.io |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 0 | 1 |
| Spec score · Software Composition Analysis Software | 7.8 (#31) | 8.4 (#8) |
| License | The repository says cargo-deny is available under either the Apache License 2.0 or MIT license, at the user's option. | The ScanCode.io software is licensed under Apache License 2.0. |
| Purpose | cargo-deny is a Cargo plugin for linting a project’s dependency graph against configured expectations and requirements. | ScanCode.io provides a Web UI and API for running and reviewing complex software composition analysis scans in scripted pipelines. |
Plans
In their own words
cargo-deny
cargo-deny has no write-up on Specifiction yet; its figures are above.
ScanCode.io
ScanCode.io provides a web interface and API for running software composition analysis scans in scripted pipelines. It scans containers, Docker images, package archives, and manifests for license, copyright, source, and vulnerability information, and can generate or consume CycloneDX and SPDX SBOMs. The same capabilities are available through its command-line interface and REST API. Documented pipeline integrations include GitHub Actions, Jenkins, GitLab, and Azure Pipelines; other CI/CD systems that support Docker can run it too. It can fetch packages using Package URLs and retrieve artifacts from JFrog Artifactory and Sonatype Nexus. Installation is preferably through Docker, including for Windows; Linux server installation is also supported, and an offline Docker package can be transferred to an isolated server. The software is open source under Apache License 2.0 and is free. Authentication for the web interface and API is disabled by default, but can be enabled. Its default setup starts one worker, so it runs one pipeline at a time.