3 maintainers
Metadata
3 maintainers
Release files for bits-mx 2.0.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 | |
|---|---|---|---|---|
| bits_mx-2.0.0.tar.gz | 4.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bits_mx-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.8 kB
Release files / bits_mx-2.0.0.tar.gz
| Download URL | bits_mx-2.0.0.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a9dae66f60c3339b28495105622c44f9898e3a2fc2229a8d727c051a68d9424a
|
|
BLAKE2b-256 checksum How to use checksums |
27677992879ae9cda9a00ac46c02faf8f0f1df96a85d6a2302deea2354433461
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.1 CPython/3.12.3 Linux/6.17.0-1010-azure
|
Release files / bits_mx-2.0.0-py3-none-any.whl
| Download URL | bits_mx-2.0.0-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7700ad4bb51b001740d281616ffd10274a4576348821deb3fc59f05a1a98462d
|
|
BLAKE2b-256 checksum How to use checksums |
27f4cd06037b77f1e3f7edb63f276425c68d80c9d1112fdffe42f0fc51dd46ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.1 CPython/3.12.3 Linux/6.17.0-1010-azure
|
Security for bits-mx 2.0.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.
