SBOM Workbench vs ScanCode.io

SBOM Workbench is a graphical tool for scanning and auditing source code through the SCANOSS API. It identifies open-source components, including undeclared code that may not appear in dependency manifests, and the free version identifies licenses and security vulnerabilities. It generates SPDX-Lite software bills of materials; release notes also list CycloneDX, SPDX Lite, CSV, and HTML exports. The tool is aimed at developers and runs on Linux, macOS, and Windows. Its CLI can use multiple SCANOSS API endpoints, including custom servers. Listed integrations include pre-commit hooks, Actions, pipelines, and webhooks, while Bitbucket is marked as coming soon. Repository documentation describes a collaborative workspace. The distributed software is described by SCANOSS as open source, and the Workbench has a public GitHub repository. Cryptographic algorithm identification is a premium feature, not included in the free Workbench. It is free to download, and SCANOSS directs support requests to email. Paid SCANOSS subscription prices listed for other offerings are not Workbench prices.

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.