ScanCode.io
scancode.io
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What ScanCode.io is
ScanCode.io is an open-source software composition analysis tool with a web interface and API for scripted scans. It examines containers, Docker images, package archives, and manifests for license, copyright, source, and vulnerability information. Teams can generate and consume CycloneDX and SPDX SBOMs, and run scans in CI/CD pipelines through integrations including GitHub Actions, GitLab, Jenkins, and Azure Pipelines. The web interface’s capabilities are also available through the command line and REST API. ScanCode.io can fetch packages using Package URLs and retrieve artifacts from JFrog Artifactory and Sonatype Nexus. Docker is the preferred installation method and works across operating systems; Linux server installation is also supported. Windows use requires Docker. It can also be installed offline on an isolated server. The software is free under Apache License 2.0 and can be self-hosted. Authentication for the web interface and API is disabled by default but can be enabled. The default configuration starts one worker, so only one pipeline runs at a time.
Who it suits
ScanCode.io suits teams automating scans for licenses, vulnerabilities, and compliance issues in CI/CD pipelines. It may also fit organizations that need self-hosted or offline installation and SBOM support.
Good to know, and what to watch
- Scans containers, archives, and manifests
- Generates and consumes CycloneDX and SPDX SBOMs
- Integrates with GitHub Actions, GitLab, and Jenkins
- Free under Apache License 2.0
- Supports offline installation
- Windows use requires Docker
- Authentication is disabled by default
- Default setup runs one pipeline at a time
Plans
Every plan and priceScanCode.io (Apache-2.0 software)
Open source
Getting started
- Open https://scancode.io/
- Install with Docker, or use the supported Linux server installation
- On Windows, run ScanCode.io through Docker
- Connect the Web UI, command-line interface, or REST API to your workflow
- Add a documented CI/CD integration such as GitHub Actions, GitLab, Jenkins, or Azure Pipelines
- Enable authentication with SCANCODEIO_REQUIRE_AUTHENTICATION when required
Limits to check
The default configuration starts one worker, so only one pipeline executes at a time. Windows use is limited to Docker-based operation.
The Club's review
Overview
ScanCode.io is a self-hosted software composition analysis platform with a web interface and API for running and reviewing scans. It is best suited to teams building license, vulnerability, and compliance checks into CI/CD pipelines. Its range of scan and SBOM workflows makes it a capable free option, provided teams can manage deployment and security settings.
Key features
ScanCode.io scans containers, Docker images, package archives, and manifests for license, copyright, source, and vulnerability information. That range helps teams assess both packaged artifacts and manifests in the same workflow. It can generate and consume CycloneDX and SPDX SBOMs, and supports pull request scanning.
The web interface's capabilities are also available through a command-line interface and REST API. Documented CI/CD integrations include GitHub Actions, Jenkins, GitLab, and Azure Pipelines; other systems can run it if they support Docker. Webhooks and Slack notifications can surface project updates. Package retrieval supports Package URLs, with examples for Cargo, RubyGems, and npm, while artifact retrieval supports JFrog Artifactory and Sonatype Nexus.
Supported ecosystems include npm, PyPI, Maven, NuGet, RubyGems, Cargo, Composer, Conda, and Docker, alongside Java, Scala, Kotlin, Groovy, Clojure, JavaScript, TypeScript, Go, Rust, Python, and Debian. This gives teams working across varied stacks a broad starting point for automated analysis.
Pricing
ScanCode.io is free open-source software under Apache License 2.0. Its ScanCode.io plan costs nothing and runs as a Docker container or on a Linux server. No commercial plan or usage limits are stated, making it a strong fit for teams able to operate their own deployment without a software subscription.
Platforms
ScanCode.io supports API, Linux, macOS, web, Windows, and self-hosted use. Docker is the preferred installation and works across operating systems; Linux server installation is also supported. Windows users must run it with Docker. An offline Docker installation package can be built and transferred to an isolated server, which suits environments without network access.
Who it's for
It suits engineering and compliance teams that want to automate software composition scans in CI/CD, review findings through a web interface or API, and work with CycloneDX or SPDX SBOMs. Teams with package sources or artifact repositories can draw on its retrieval support. It is less suitable for organizations expecting multiple pipelines to run concurrently without changing the default configuration: the installation starts one worker, so only one pipeline executes at a time.
Authentication for the web interface and REST API is disabled by default. Administrators can enable it with the SCANCODEIO_REQUIRE_AUTHENTICATION setting; when enabled, REST API users can authenticate with an API key in the Authorization header. That flexibility calls for an explicit security setup before exposing the service. Generated data is provided as-is, without warranties, and is not legal advice.
Pros and cons
- Pros: Broad scan targets and support for both generating and consuming CycloneDX and SPDX SBOMs serve teams with varied artifact workflows.
- Pros: A web interface, CLI, REST API, and documented CI integrations support both review and pipeline automation.
- Pros: Free Apache-2.0 software can run self-hosted, including in an offline Docker deployment.
- Cons: The default single worker serializes pipeline execution, a constraint for teams that need concurrent scans.
- Cons: Authentication is disabled by default, so teams must configure it when the deployment needs protected access.
- Cons: Windows support requires Docker, which rules out a native Windows installation.
Alternatives
For a managed free tier with explicit project and contributor caps, consider FOSSA: its free plan allows five projects, 10 contributing developers, one release group, scans to five dependency levels, and one quality check. Choose FOSSology for an open-source license compliance toolkit and system. ScanCode Toolkit is another free software code scanning tool.
DejaCode is a paid option with a free plan and trial; its repository is licensed under AGPL-3.0. Double Open Compliance offers a free SaaS tier and a Pro plan. Choose REUSE Tool for a free tool that needs no registration and can run offline. SBOM Workbench is a free download with a public GitHub repository. SW360 is a free, self-managed option under EPL-2.0.
Readers comparing more products can browse open-source license compliance software and software composition analysis software.
Verdict
ScanCode.io is a sound choice for teams that want a free, self-hosted platform to automate broad composition scans and SBOM workflows across CI/CD. Its flexible interfaces, integrations, and offline deployment support are strong reasons to choose it. Look elsewhere if you need concurrent pipelines out of the box or prefer a service with access controls already enabled.
The verdict
ScanCode.io combines scan review, SBOM handling, and pipeline automation in a free self-hosted tool. Teams should account for the default single-worker setup and configure authentication when needed.
Questions people ask
Is ScanCode.io free?
Yes. The listed ScanCode.io plan costs nothing, and the project is open source under Apache License 2.0.
Which platforms can run it?
Its listed platforms are API, Linux, macOS, self-hosted, web, and Windows. Windows operation requires Docker.
What can it scan?
It scans containers, Docker images, package archives, and manifests for license, copyright, source, and vulnerability information.
Does it support SBOMs?
Yes. ScanCode.io can generate and consume CycloneDX and SPDX SBOMs.
Can it run offline?
Yes. The installation guide describes building and transferring an offline Docker installation package for an isolated server.
How is API authentication handled?
Web UI and REST API authentication is disabled by default. It can be enabled with SCANCODEIO_REQUIRE_AUTHENTICATION, and the REST API then supports an API key in the Authorization header.
What the maker publishes
- Artifact repositories
- It can fetch artifacts from JFrog Artifactory and Sonatype Nexus repositories. source
- Authentication
- Web UI and REST API authentication is disabled by default and can be enabled through the SCANCODEIO_REQUIRE_AUTHENTICATION setting. source
- Authentication options
- When authentication is enabled, users can authenticate to the REST API with an API key in the Authorization header. source
- CI/CD integrations
- Documented CI/CD integrations include GitHub Actions, GitLab, and Azure Pipelines; other Docker-capable CI/CD systems can also run it. source
- CI integrations
- The automation guide documents integrations for GitHub Actions, Jenkins, GitLab, Azure Pipelines, and other Docker-capable CI systems. source
- Deployment
- The preferred installation is with Docker, which the documentation says works across all operating systems; Linux server installation is also supported. source
- Deployment
- ScanCode.io can run in a Docker container or be installed on a Linux server. source
- Founded
- 2014 source
- Headquarters
- Brussels, Belgium source
- Interfaces
- The Web UI capabilities are also available through the command-line interface and REST API. source
- License
- The ScanCode.io software is licensed under Apache License 2.0. source
- License and warranty
- The software is licensed under Apache-2.0, and the project says generated data is provided as-is without warranties and is not legal advice. source
- Notifications
- ScanCode.io supports webhooks and Slack notifications for project updates. source
- Notifications
- Project webhooks can send pipeline updates to external services, with built-in support for Slack Incoming Webhooks. source
- Offline use
- The installation guide describes building and transferring an offline Docker installation package for an isolated server. source
- Offline use
- The installation guide describes running ScanCode.io on an internet-isolated server using Docker images transferred from an internet-connected machine. source
- Package sources
- It can fetch packages using Package URLs and supports examples from Cargo, RubyGems, and npm. source
- Purpose
- ScanCode.io provides a Web UI and API for running and reviewing complex software composition analysis scans in scripted pipelines. source
- SBOMs
- It supports generating and consuming CycloneDX and SPDX SBOMs. source
- SBOM support
- It supports generating and consuming CycloneDX and SPDX SBOMs. source
- Scaling limit
- The installation guide says the default configuration starts one worker, so only one pipeline executes at a time. source
- Scan targets
- It scans containers, Docker images, package archives, and manifests for license, copyright, source, and vulnerability information. source
- Security configuration
- Authentication for the Web UI and REST API is disabled by default and can be enabled with SCANCODEIO_REQUIRE_AUTHENTICATION. source
- Software composition analysis
- ScanCode.io provides a Web UI and API for scripted scans that report on licenses, copyrights, sources, and vulnerabilities. source
Checked against the maker's pages on 11 Oct 2026.