Sandworm Audit vs ScanCode.io
Sandworm Audit
sandworm.devScanCode.io
scancode.ioSide by side
| Figure | Sandworm Audit | ScanCode.io |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Software Composition Analysis Software | 7.2 (#52) | 8.4 (#8) |
| Purpose | Sandworm Audit scans a project and its dependencies for vulnerabilities, license issues, and metadata issues. | ScanCode.io provides a Web UI and API for running and reviewing complex software composition analysis scans in scripted pipelines. |
| Support | The documentation directs support questions and feature requests to GitHub discussions and bug reports to GitHub issues. | The documentation directs users to file documentation issues for missing or confusing content. |
Plans
In their own words
Sandworm Audit
Sandworm Audit 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.