license-audit
Analyze dependency licenses for Python projects.
license-audit tells you what license your project can use, flags incompatible combinations, and generates compliance documents suitable for CI gating.
Features
- License detection across the full transitive tree, from PEP 639 metadata, the legacy
Licensefield, trove classifiers, and user overrides. - Pairwise compatibility checking against the OSADL compatibility matrix (~120 licenses).
- Outbound license recommendations ranked by permissiveness.
- Compliance reports as Markdown, JSON, or third-party-notices.
- CI exit codes that distinguish policy violations from undetected licenses.
- Reads the licenses straight from your installed environment: provision it however you like (
uv, Poetry, pip), then point license-audit at it.
Installation
pip install license-audit
Or with uv:
uv add license-audit --dev
Quickstart
Provision your dependencies first, then run license-audit inside that environment:
uv sync
uv run license-audit analyze
Or point it at an existing virtualenv:
license-audit --target .venv analyze
───────────────────── License Analysis: my-project ─────────────────────
Source: /path/to/my-project/.venv
Dependency Licenses
┏━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━━┓
┃ Package ┃ Version ┃ License ┃ Category ┃ Source ┃ Parent ┃
┡━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━━┩
│ click │ 8.3.1 │ BSD-3-Clause │ permissive │ pep639 │ (direct) │
│ pydantic │ 2.12.5 │ MIT │ permissive │ pep639 │ (direct) │
│ rich │ 14.3.0 │ MIT │ permissive │ pep639 │ (direct) │
└──────────┴─────────┴──────────────┴────────────┴────────┴──────────┘
Recommended Outbound Licenses (most -> least permissive):
-> MIT
Apache-2.0
BSD-2-Clause
BSD-3-Clause
ISC
... and 111 more
──────────────────────────────── Summary ───────────────────────────────
Total dependencies: 3
Unknown licenses: 0
Copyleft licenses: 0
Policy check: PASSED
Commands
| Command | Purpose |
|---|---|
analyze |
Per-package analysis in the terminal, or as JSON with --format json |
check |
CI policy gate with distinct exit codes |
report |
Compliance documents: Markdown, JSON, or third-party notices |
recommend |
Outbound license recommendation with guidance |
refresh |
Re-download the OSADL compatibility data |
See the commands reference for details.
CI quickstart
Add to your pipeline to gate on license policy:
jobs:
license-check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: astral-sh/setup-uv@v5
- run: uv sync --locked
- run: uv run license-audit check
Exit codes:
| Code | Meaning |
|---|---|
0 |
All dependencies pass the policy |
1 |
Policy violation (incompatible pairs, denied licenses, or category exceeded), or the check could not run |
2 |
Unknown licenses detected and no other violation (when fail-on-unknown = true) |
For GitLab, pre-commit, handling unknowns, and the new-dependency workflow, see the CI integration guide.
Configuration
[tool.license-audit]
fail-on-unknown = true
policy = "permissive" # permissive | weak-copyleft | strong-copyleft | network-copyleft
allowed-licenses = ["MIT", "Apache-2.0", "BSD-3-Clause"]
denied-licenses = ["GPL-3.0-only"]
target = ".venv" # optional; defaults to ./.venv, else the active environment
[tool.license-audit.overrides]
some-internal-package = "MIT"
dual-licensed-pkg = "Apache-2.0 OR MIT"
[tool.license-audit.license-classifications]
"CNRI-Python" = "permissive" # your judgement for licenses OSADL doesn't cover
[tool.license-audit.ignored-packages]
pandas-stubs = "Stubs only, not redistributed"
Full reference: user guide -> configuration.
Documentation
Full documentation lives at https://dgeragh.github.io/license-audit:
License
MIT. See LICENSE.
This project bundles data from the OSADL Open Source License Obligations Checklists project, licensed under CC-BY-4.0. See THIRD_PARTY_NOTICES.md for full attribution.
Metadata
Release files for license-audit 0.14.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 | |
|---|---|---|---|---|
| license_audit-0.14.0.tar.gz | 177.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| license_audit-0.14.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 239.0 kB
Release files / license_audit-0.14.0.tar.gz
| Download URL | license_audit-0.14.0.tar.gz |
|---|---|
| Size | 177.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
972cab807315f0544cf9bd9a959a01ebe5688df89de7467fbe91b6c366e6c85d
|
|
BLAKE2b-256 checksum How to use checksums |
e324d04f0941e532154cd89e1d198646c030144b36d355457aff680e9378cc9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / license_audit-0.14.0-py3-none-any.whl
| Download URL | license_audit-0.14.0-py3-none-any.whl |
|---|---|
| Size | 61.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec3c037b7452c08535f7d3260e7a365289383dd5297e093c52eac19ceaed1028
|
|
BLAKE2b-256 checksum How to use checksums |
ade7f2000fd67ca21ff357f680a3c6187de6af645bc02460159e2d61e7255d48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logSecurity for license-audit 0.14.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for license_audit-0.14.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 Sep 5, 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.