1 maintainer
Metadata
1 maintainer
Release files for sphinx-licenseinfo 0.7.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 | |
|---|---|---|---|---|
| sphinx_licenseinfo-0.7.0.tar.gz | 12.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sphinx_licenseinfo-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.7 kB
Release files / sphinx_licenseinfo-0.7.0.tar.gz
| Download URL | sphinx_licenseinfo-0.7.0.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3dc725152b3c16a8d518d1e0a268bf38674e54700f2b30127c42ff63330372cd
|
|
BLAKE2b-256 checksum How to use checksums |
791f2a89405222722a38dbc0a037e36883434498b9bbb2a9841df149eda4e4ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / sphinx_licenseinfo-0.7.0-py3-none-any.whl
| Download URL | sphinx_licenseinfo-0.7.0-py3-none-any.whl |
|---|---|
| Size | 14.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eaa6f3d7f66eac200b1dbcfc7ffa8d87b76c90208f888fe4cfb45926ce497ed5
|
|
BLAKE2b-256 checksum How to use checksums |
42f379ebe167cdca916b71df671759e7783c5bd7bf9a1db7fbf03cbfe8d169a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for sphinx-licenseinfo 0.7.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
