finds.dev

aboutcode-org/scancode-toolkit

ScanCode detects licenses, copyrights, dependencies by "scanning code" ... to discover and inventory open source and third-party packages used in your code. Sponsored by NLnet, the Google Summer of Code, Azure credits, nexB and other generous sponsors!

View on GitHubHomepage ↗

★ 2,656PythonNOASSERTIONupdated Oct 2026

// the take

ScanCode Toolkit is a CLI/library for scanning codebases to detect licenses, copyrights, and package dependencies, producing SBOM-style output (SPDX, CycloneDX, JSON). It's aimed at compliance teams and tooling authors who need to know what licenses and third-party components are actually in a codebase, not just what package.json claims.

License detection is rules-based and does actual text comparison against a license database rather than relying purely on regex or fuzzy matching, which makes it noticeably more accurate on edge cases (dual licenses, modified license headers, embedded license snippets) than lighter tools. It has a real test suite (30k+ tests) run across Linux/macOS/Windows, and it's been battle-tested as the backend for other tools (ClearlyDefined, OSS Review Toolkit, ScanCode.io), so the core engine isn't speculative. Output formats cover what compliance workflows actually need (SPDX, CycloneDX, JSON/YAML, HTML app, custom Jinja templates), and the plugin architecture lets you add new scanners or package parsers without forking the core.

It's slow on large codebases — full license+copyright+package scans on anything beyond a mid-size repo can take a long time since it's doing real text comparison rather than hashing, and there's no obvious incremental/diff scan mode in the base CLI (that's pushed to the separate ScanCode.io project). Python packaging is heavy: native dependencies and a large bundled license database make install and Docker image size nontrivial, and version pinning across the ecosystem (scancode-toolkit vs scancode.io vs purldb) is a recurring source of friction. It detects what's in the code, not what's legally enforceable — license conflict analysis, obligation tracking, and policy enforcement are explicitly left to commercial tooling or ScanCode.io, so this alone doesn't give you a compliance sign-off, just raw scan data you still have to interpret.

We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
2,656
Forks
831
Language
Python
License
NOASSERTION
Last commit
28 Oct 2026

// nearby

If scancode-toolkit isn't quite it.

All repos →