taloon
Check declared licenses of Python dependencies in uv.lock, including development
and transitive dependencies. Implemented in Rust.
Usage
Add a license policy to the pyproject.toml in the same directory as uv.lock:
[tool.taloon]
schema-version = 1
allow = ["MIT", "Apache-2.0"]
After installing taloon, run from your project directory:
taloon check
taloon check --format json
Exit codes are 0 for compliance, 1 for a policy violation or escalated warning,
and 2 for invalid input or incomplete inspection.
Documentation
- User guide: installation, supported platforms, Python versions, and release availability.
- License policy: allowlists, exceptions, and clarifications.
- Commands and automation: CLI options, offline mode, and hooks.
- Development guide: building, testing, and contributing.
- Design decisions: contracts and architecture.
- Release procedure: wheel builds, publication, and recovery.
Licensed under the Elastic License 2.0.
1 maintainer
Metadata
1 maintainer
Release files for taloon 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| taloon-0.1.3-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for taloon-0.1.3-py3-none-win_amd64.whl |
| taloon-0.1.3-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details for taloon-0.1.3-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| taloon-0.1.3-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for taloon-0.1.3-py3-none-macosx_11_0_arm64.whl |
Total release size: 9.8 MB
Release files / taloon-0.1.3-py3-none-win_amd64.whl
| Download URL | taloon-0.1.3-py3-none-win_amd64.whl |
|---|---|
| Size | 3.1 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
260c6537908021fd164531fdf845710a5b6b5bb675cc9ebdb9bd36256814ebdc
|
|
BLAKE2b-256 checksum How to use checksums |
d3c4b870a111c43f218210b863fdb5f4aca4529f3ed534fcdaa6537992ca3664
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 1, 2026.
Transparency log
SLSA Build Provenance Attestation
PyPI verified that this artifact, at this checksum, originated from the builder listed below.
Built by GitHub Actions, verified by PyPI on Nov 1, 2026.
Transparency logRelease files / taloon-0.1.3-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | taloon-0.1.3-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 3.4 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
8c00b07de83bc86d1d267f95bbd2d89eea9f96259f20edcf3af2b5574ac11ea4
|
|
BLAKE2b-256 checksum How to use checksums |
7618d871cf2f2781163481870bcca9fea5d9b733339d6efd103011cb3901a3c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 1, 2026.
Transparency logSLSA Build Provenance Attestation
PyPI verified that this artifact, at this checksum, originated from the builder listed below.
Built by GitHub Actions, verified by PyPI on Nov 1, 2026.
Transparency logRelease files / taloon-0.1.3-py3-none-macosx_11_0_arm64.whl
| Download URL | taloon-0.1.3-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.2 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
cc443c7df5d86e22b8c514530b33678ed79a9d5245476ed3c6d33de7f09bd04c
|
|
BLAKE2b-256 checksum How to use checksums |
5c83999e9eb6a798f7e4f54fe914785550c3bc2fc714982801a78d928b510bab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 1, 2026.
Transparency logSLSA Build Provenance Attestation
PyPI verified that this artifact, at this checksum, originated from the builder listed below.
Built by GitHub Actions, verified by PyPI on Nov 1, 2026.
Transparency logSecurity for taloon 0.1.3
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 3 files in this release have been uploaded with provenance metadata.
Attestations for taloon-0.1.3-py3-none-win_amd64.whl
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 Nov 1, 2026.
Transparency logSLSA Build Provenance Attestation
PyPI verified that this artifact, at this checksum, originated from the builder listed below.
Built by GitHub Actions, verified by PyPI on Nov 1, 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.
