1 maintainer
Metadata
1 maintainer
Release files for bbqudit 0.0.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 | |
|---|---|---|---|---|
| bbqudit-0.0.1.tar.gz | 317.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bbqudit-0.0.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 626.8 kB
Release files / bbqudit-0.0.1.tar.gz
| Download URL | bbqudit-0.0.1.tar.gz |
|---|---|
| Size | 317.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
69ef9bee773f59b052156b70ee45dea5a92a8ddd1dd406ef5a0b59d75114ed7b
|
|
BLAKE2b-256 checksum How to use checksums |
2415a79bcf33efac0b05dc2eb4aa47a5a3c9bc67a236a2ed9496cae237ffbe94
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.1
|
Release files / bbqudit-0.0.1-py2.py3-none-any.whl
| Download URL | bbqudit-0.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 309.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7418e7a4956990e0d34251b93023332fba63a7f10adc8c1607bb61a05c552283
|
|
BLAKE2b-256 checksum How to use checksums |
16215c0f2d1e965b1e6b178dd3e2f0627d04302b26e1cd266853a9ae6de82b2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.1
|
Security for bbqudit 0.0.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.
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.
