3 maintainers
Metadata
3 maintainers
Release files for bits-mhl 1.21.6
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 | |
|---|---|---|---|---|
| bits_mhl-1.21.6.tar.gz | 10.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bits_mhl-1.21.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.8 kB
Release files / bits_mhl-1.21.6.tar.gz
| Download URL | bits_mhl-1.21.6.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
26fc14abbb294782e5c48dfc94dc0e6163b6b8d63f57ef518bef4f94daeb6e57
|
|
BLAKE2b-256 checksum How to use checksums |
712116fc3165c59be2757d4f938bab568e040caf79b7d0af3daf0c662b51a3ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.4 CPython/3.12.3 Linux/6.11.0-1018-azure
|
Release files / bits_mhl-1.21.6-py3-none-any.whl
| Download URL | bits_mhl-1.21.6-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
19cbfae5b3a43238d0af0d5ca7c02303d6b2b5d5e95f6837330bbcd0903dba9e
|
|
BLAKE2b-256 checksum How to use checksums |
ef735e91a52e1c69f2ba56046c8300b07a197b27ac16955575deb38fd2e2810d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.4 CPython/3.12.3 Linux/6.11.0-1018-azure
|
Security for bits-mhl 1.21.6
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.
