LicenseID
A portable license ID matcher. Get the SPDX License ID from license text.
licenseid takes license text as input and identifies the closest matched SPDX License ID using a hybrid search strategy (trigram + token ratio ranking).
Features
- Hybrid strategy:
- Tier 0 (Shortcut): Immediate identification for exact license names and IDs.
- Tier 1 (Recall): Rapid candidate retrieval using SQLite FTS5 (trigram) with query truncation for performance.
- Tier 2 (Precision): Adaptive ranking using RapidFuzz with boosting for canonical matches.
- Tier 3 (Validation): Optional final validation via
tools-javaif available.
- Unix philosophy: Parseable, line-delimited CLI output.
- Performance: Sub-second matching for most licenses; optimized for large file handling.
Installation
Install with pipx:
pipx install licenseid
Or using uv:
uv tool install licenseid
Usage
1. Update the license database
Before matching, you need to build the local license index:
licenseid update
Advanced update options:
--version <version>: Download a specific SPDX License List version (e.g.,3.28.0).--force: Force update even if the local database is already at the target version.--no-cache: Bypass the local cache for downloads.
2. Match a license
Identify license text from a file:
licenseid match LICENSE.txt
Or match from a string:
licenseid match --text "Apache License\nVersion 2.0"
The --text argument supports standard escape sequences (e.g., \n, \t, \") which are automatically unescaped before matching.
Common options:
--diff: Show a word-by-word diff between the input and the best-matching candidate.--java: Enable Tier 3 Java validation (requiresSPDX_TOOLS_JARandjpype1).--pop: Enable popularity weighting as a tie-breaker.--json: Output results in JSON format.--db <path>: Use a custom database path (global option). Supports SQLite URIs for in-memory databases (e.g.,file:test?mode=memory&cache=shared).
The system uses a composite score (Similarity + Coverage + Popularity) to ensure the "tightest" match is preferred (e.g., distinguishing between a license and its supersets).
3. Cache management
licenseid maintains a local cache of remote data to save bandwidth.
licenses.json: Cached for 45 days.popularity.csv: Cached for 75 days.- SPDX data tarballs are versioned and never expire.
To clear the cache manually:
licenseid --clear-cache
4. Output formats
Default (Unix-friendly):
LICENSE_ID=Apache-2.0 SIMILARITY=0.9850 COVERAGE=1.0000
JSON:
licenseid match LICENSE.txt --json
Diff (visual comparison):
licenseid match LICENSE.txt --diff
Example output:
LICENSE_ID=Apache-2.0 SIMILARITY=0.9980 COVERAGE=0.9975
WORD DIFF:
--- DATABASE
+++ INPUT
@@ -1601,8 +1601,4 @@
language
governing
permissions
-and
-limitations
-under
-the
-license
+se
Development
Running Tests
Regular test suite:
pytest
Run benchmarks and accuracy tests (expensive):
pytest --run-benchmark
Configuration
SPDX_TOOLS_JAR: Path to thetools-javajar for Tier 3 validation.
License
Apache-2.0
Metadata
Release files for LicenseID 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| licenseid-0.2.0.tar.gz | 30.7 kB | With provenance | Details for licenseid-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| licenseid-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for licenseid-0.2.0-py3-none-any.whl |
Total release size: 51.1 kB
Release files / licenseid-0.2.0.tar.gz
| Download URL | licenseid-0.2.0.tar.gz |
|---|---|
| Size | 30.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e1e8397a468258cbae2d38806d64162f9e4d32d5926887059902525a65efa9c
|
|
BLAKE2b-256 checksum How to use checksums |
3b591e373f96fe4c3c4981aa0576eae72415ab2877c80dd4fb06fec2653ab0cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 28, 2026.
Transparency logRelease files / licenseid-0.2.0-py3-none-any.whl
| Download URL | licenseid-0.2.0-py3-none-any.whl |
|---|---|
| Size | 20.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
70ce43acd3a50e978403865b4cde4fdf80b2d9176571cf443c205420579ee401
|
|
BLAKE2b-256 checksum How to use checksums |
c6c6090d4b36770b923f0e961c3c340276ed6eac26c87bdfb2c1bf1e19ba033c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 28, 2026.
Transparency logSecurity for LicenseID 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for licenseid-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.