OSSKB vs ScanCode.io

OSSKB identifies open source software in source code, including at the snippet level, to provide information relevant to license compliance. It matches source-code fingerprints against a database of fingerprints for known open source software. Results may include license names, copyright statements, quality indicators, and vulnerability information. The web service also offers API access, a Python scanner, and Audit Workbench downloads for macOS Intel, macOS M1/M2, and Linux; a compatible CLI or webhook can support automation. OSSKB is powered by the Open Source Software Knowledge Base, created and maintained by SCANOSS. It is free of charge on a best-effort basis, with no guarantee of availability or performance. The provider may limit the number or frequency of transactions to help maintain availability and performance. Fingerprint matching can produce false positives and false negatives, so results need human assessment. The terms say usage information may be logged to monitor load and improve the service, and that OSSKB is designed for professional use rather than end consumers. The listed plan is free.

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.