python-sbom
Software bills of materials (SBOMs) for Python distributions. python-sbom writes a CycloneDX SBOM into every wheel you build, where PEP 770 (a Python Enhancement Proposal) tells installers to keep it. The SBOM records your project, the runtime dependencies it declares, any wheels it bundles, and the build toolchain, and a rebuild with the same inputs reproduces it byte for byte.
Use
python-sbom works with every build backend. Pick the integration for yours:
| Backend | Add to [build-system] requires |
Turn it on |
|---|---|---|
| hatchling | python-sbom[hatch] |
[tool.hatch.build.hooks.python-sbom] |
| pdm-backend | python-sbom[pdm] |
[tool.python-sbom] |
| setuptools | python-sbom[setuptools] |
[tool.python-sbom] |
| any other, such as meson-python, maturin, scikit-build-core or flit-core | python-sbom |
build-backend = "python_sbom.backend", and your backend in [tool.python-sbom] |
With hatchling:
[build-system]
build-backend = "hatchling.build"
requires = ["hatchling>=1.28", "python-sbom[hatch]>=0.2"]
[tool.hatch.build.hooks.python-sbom]
With meson-python, or any backend without a plugin, python-sbom wraps it:
[build-system]
build-backend = "python_sbom.backend"
requires = ["meson-python>=0.18", "python-sbom>=0.2"]
[tool.python-sbom]
build-backend = "mesonpy"
For a wheel built outside the build interface, such as with maturin build, or renamed after
it by auditwheel repair, embed the SBOM afterwards:
python-sbom embed dist/*.whl
To convert and validate SBOMs in continuous integration (CI), install the command line in a tool environment of its own with pipx or uv:
pipx install 'python-sbom[validate]'
python-sbom validate dist/
The documentation starts with a tutorial, then has a guide per backend, the options and commands, and how the SBOM is built. It also covers describing a zipapp, adding project knowledge through a content provider, and rendering an SBOM as SPDX (Software Package Data Exchange).
1 maintainer
Metadata
1 maintainer
Release files for python-sbom 0.3.1
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 |
|---|---|---|---|---|
| python_sbom-0.3.1.tar.gz | 289.5 kB | With provenance | Details for python_sbom-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| python_sbom-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for python_sbom-0.3.1-py3-none-any.whl |
Total release size: 494.6 kB
Release files / python_sbom-0.3.1.tar.gz
| Download URL | python_sbom-0.3.1.tar.gz |
|---|---|
| Size | 289.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37d0fa3d0a16fddc3d88099e147e164ddb3055e8bc3424506ef41dd80f723a73
|
|
BLAKE2b-256 checksum How to use checksums |
e7c8433fce09ca6d9580e71b1bcde4db4da5c1f77039536deca9d373f1b7886e
|
| 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 10, 2026.
Transparency logRelease files / python_sbom-0.3.1-py3-none-any.whl
| Download URL | python_sbom-0.3.1-py3-none-any.whl |
|---|---|
| Size | 205.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fd7a64f0293c033ac8ed8946c3c2513e936eacb7c297fe5110e5bb06d42aafc9
|
|
BLAKE2b-256 checksum How to use checksums |
4d14f144bdd2ced56c3ffb5e6f85761a8ed203955de25f56803cebf584db2b71
|
| 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 10, 2026.
Transparency logSecurity for python-sbom 0.3.1
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 python_sbom-0.3.1.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 Nov 10, 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.
