Check License Compliance vs ScanCode.io
Check License Compliance
github.comScanCode.io
scancode.ioSide by side
| Figure | Check License Compliance | 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 | Yes |
| Plans published | 1 | 1 |
| Spec score · Open Source License Compliance Software | 8.0 (#9) | 8.4 (#5) |
| Deployment | The GitHub Action runs using a Docker image defined by the repository's Dockerfile. | ScanCode.io can run in a Docker container or be installed on a Linux server. |
| Purpose | Checks repository dependencies against allowed, forbidden, and warning license policies. | 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
Check License Compliance
Check License Compliance 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.