Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

ScanCode Toolkit

scancode-toolkit.readthedocs.io

  • Free plan
  • Windows
  • macOS
  • Linux
  • API
  • Self-hosted

What ScanCode Toolkit is

ScanCode Toolkit is a free tool for scanning codebases for code origin, copyrights, licenses, vulnerabilities, packages and dependencies. It can run from the command line or work as a library inside an application. Its license detector checks extracted file text against an index of license texts and rules; scanning can also unpack archives recursively and extract text from binary files when needed. It recognizes package manifests, lockfiles and other package datafiles. Results can be saved as JSON, YAML, JSON Lines, HTML, SPDX, Debian copyright or CycloneDX; CSV is marked deprecated. JSON output can be used by ScanCode Workbench and other applications that accept ScanCode result data. Plugins extend processing stages, and external plugins can add license data. Installation choices include release archives, Docker, source, pip and Fedora’s repository. The documentation lists Linux, macOS and Windows as tested platforms, with 64-bit operating system and Python requirements. The project directs users to community Slack and GitHub discussions for help. Its output comes without warranties and is not legal advice.

Who it suits

It suits developers and organizations that need to examine codebases for licenses, origins, vulnerabilities and dependencies. It can also fit teams that want command-line scanning or integration into an application.

Good to know, and what to watch

  • Free software code scanning tool.
  • Runs from the command line or as an application library.
  • Recognizes package manifests, lockfiles and package datafiles.
  • Supports multiple structured and reporting output formats.
  • Plugins can extend scanning and add license data.
  • CSV output is marked deprecated.
  • Documentation specifies 64-bit systems and Python requirements.
  • Scan output is not legal advice and comes without warranties.

ScanCode Toolkit

Free

Free plan

Getting started

  1. Open the ScanCode Toolkit documentation
  2. Choose release archive, Docker, source, pip, or Fedora installation
  3. Use a documented 64-bit Linux, macOS, or Windows environment with Python requirements
  4. Run scans from the command line or integrate the library into an application
  5. Select JSON, YAML, JSON Lines, HTML, SPDX, Debian copyright, or CycloneDX output
  6. Use community Slack or GitHub discussions for questions

Limits to check

The ScanCode Toolkit plan is free. CSV results are marked deprecated, and documented platform requirements include a 64-bit operating system and Python.

The Club's review

ScanCode Toolkit is a free, self-hosted scanner for code origin, licensing, vulnerabilities, packages and dependencies. It suits developers, engineering teams and compliance specialists who can work with command-line or library tooling. The trade-off is a technically rich, flexible toolkit rather than a managed service or a legal opinion.

Overview

ScanCode Toolkit examines codebases for provenance, copyright notices, license matches, vulnerabilities, packages and dependency relationships. You can run it directly from a command line or embed it as a library in an application, so it fits both one-off investigations and automated internal workflows. That flexibility favors teams building their own review process; organizations wanting a hosted interface and vendor-managed operations should look elsewhere.

The project comes from nexB, founded in 2003 by Michael J. Herzog, Philippe Ombrédanne and François Granade. Deployment is on-premise, with multiple source-scan methods and advisory policy enforcement. Scan output is supplied as-is without warranties and should not be treated as legal advice, so legal teams still need to interpret findings independently.

Key features

Code, license and archive analysis

License detection compares text extracted from files with an index of license texts and matching rules. The scanner recursively unpacks archives and can extract text from binary files when necessary, extending coverage beyond ordinary source files. This is useful when repositories contain packaged or generated material, although broader coverage also means technical findings require review before decisions are made.

Package and dependency inventory

Support for a wide range of package manifests, lockfiles and package datafiles lets ScanCode identify package and dependency information alongside license and provenance results. It is a practical foundation for software inventories and supply-chain reviews, especially where teams need one scan to feed several downstream checks.

Reports and integration

Results can be exported as JSON, YAML, JSON Lines, HTML, SPDX, Debian copyright or CycloneDX. JSON can be consumed by ScanCode Workbench and other applications that accept ScanCode result data, making it suitable for custom pipelines and software-bill-of-materials workflows. CSV is deprecated, so teams whose process depends on CSV should choose another output path or migrate.

Extensibility

Plugins can add processing at different scanning stages, and external plugins can contribute license data. That gives technical teams room to adapt the toolkit to internal rules and unusual codebases, but it also places responsibility for maintaining extensions on the user.

Pricing

ScanCode Toolkit is free software at no cost. There are no paid tiers, seat charges or stated usage quotas in the plan. The free plan is therefore the complete offering rather than a restricted entry level, which suits teams that can operate self-hosted software and manage their own infrastructure. The cost advantage comes with operational responsibility: installation, upgrades, scanning workflows and interpretation remain with your organization.

Platforms

The toolkit is offered for API, Linux, macOS, self-hosted and Windows use. Installation routes include release archives, Docker, source, pip and Fedora's repository. Documentation identifies Linux, macOS and Windows as tested platforms, with 64-bit operating-system and Python requirements that should be checked before rollout. Community Slack and GitHub discussions provide the project’s support channels.

Who it's for

Choose ScanCode Toolkit when developers or compliance engineers need detailed, machine-readable inventory data and want to run scans inside their own environment. Its command-line and library interfaces work well for repeatable pipelines, while SPDX and CycloneDX exports help teams hand results to existing supply-chain tooling. It is less suitable for buyers seeking a polished hosted service, turnkey policy decisions or advice that can substitute for legal review.

Pros and cons

Pros

  • Broad scan scope: origin, copyright, licenses, vulnerabilities, packages and dependencies are covered in one toolkit.
  • Deep file handling: recursive archive extraction and binary-text extraction can expose material a simple file walk would miss.
  • Flexible integration: command-line and library modes, plugins, and several standards-oriented export formats support custom workflows.
  • No licence fee: the complete plan costs nothing and has no stated seat or quota limits.

Cons

  • Self-managed operation: on-premise deployment and multiple installation paths require internal technical ownership.
  • Results need interpretation: advisory enforcement and the as-is, non-legal-advice limitation make it unsuitable as a standalone legal decision-maker.
  • Deprecated CSV: organizations built around CSV exports face a migration or integration compromise.
  • Environment prerequisites: 64-bit systems and Python requirements can affect rollout across mixed estates.

Alternatives

For a hosted freemium option with a free tier, five projects, ten contributing developers, one release group, five dependency levels and one quality check, choose FOSSA. If you want the same general scanning family delivered as an Apache-2.0 Docker container or Linux-server deployment with no stated commercial tier or usage limits, consider ScanCode.io. FOSSology is another free, open-source license-compliance toolkit and system.

Choose DejaCode when a paid, web-oriented team service is preferable; its Team plan is $500 a month on an annual subscription. Double Open Compliance offers a freemium SaaS route with free and Pro tiers. For an offline, registration-free tool, pick REUSE Tool. SBOM Workbench is a free desktop download for Linux, macOS and Windows. SW360 is a free, self-managed EPL-2.0 platform. Browse Open Source License Compliance Software for the wider category.

Verdict

ScanCode Toolkit is the right choice for technical teams that want a capable, no-cost scanner they can embed, automate and export into established compliance workflows. Its main reason to choose it is breadth combined with deployment and output flexibility. Look elsewhere if you need a managed user experience, commercial operational support or conclusions that go beyond advisory technical scan results.

The verdict

ScanCode Toolkit covers code, license and dependency scanning, with multiple deployment and output choices. Check its platform and Python requirements, and treat its results as informational rather than legal advice.

Questions people ask

How much does ScanCode Toolkit cost?

The listed ScanCode Toolkit plan costs nothing.

Which platforms are supported?

Documentation lists Linux, macOS, and Windows as tested platforms, with 64-bit operating-system and Python requirements. API and self-hosted use are also listed.

What output formats are available?

Results can be written as JSON, YAML, JSON Lines, HTML, SPDX, Debian copyright, or CycloneDX. CSV is marked deprecated.

Can it run inside another application?

Yes. ScanCode can operate as a command-line tool or as a library in an application.

Is ScanCode output legal advice?

No. The output is provided as-is without warranties, and its content should not be used as legal advice.

How is it installed?

Installation options include release archives, Docker, source, pip, and Fedora’s repository.

What the maker publishes

Archive scanning
The scanning process extracts files recursively from archives and extracts text from binary files when needed. source
Extensibility
Plugins can extend ScanCode at different stages, and users can add license data through external plugins. source
Founded
2003 source
Headquarters
Los Altos, California, United States source
Installation
Installation options include release archives, Docker, source, pip, and Fedora’s repository. source
Integration
JSON scan results can be consumed by ScanCode Workbench and other applications that accept ScanCode result data. source
Legal limitation
The scan output says ScanCode is provided as-is without warranties and that its content should not be used as legal advice. source
License detection
License detection searches an index of license texts and rules for matches in extracted file text. source
Maker history
nexB says it was founded in 2003 by Michael J. Herzog, Philippe Ombrédanne and François Granade. source
Output formats
Scan results can be written as JSON, YAML, JSON Lines, HTML, SPDX, Debian copyright, or CycloneDX; CSV is marked deprecated. source
Package support
It supports a wide variety of package manifests, lockfiles and package datafiles containing package and dependency information. source
Platform requirements
The documentation lists Linux, macOS and Windows as tested platforms and specifies 64-bit operating systems and Python requirements. source
Purpose
ScanCode Toolkit scans codebases to detect code origin, copyrights, licenses, vulnerabilities, packages and dependencies. source
Support
The project directs users to its community Slack and GitHub discussions for questions and challenges. source
Use modes
It can be used as a command-line tool or as a library in an application. source

Checked against the maker's pages on 2 Oct 2026.