Metadata
Release files for petal-qc 0.0.34
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 | |
|---|---|---|---|---|
| petal_qc-0.0.34.tar.gz | 159.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| petal_qc-0.0.34-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 361.7 kB
Release files / petal_qc-0.0.34.tar.gz
| Download URL | petal_qc-0.0.34.tar.gz |
|---|---|
| Size | 159.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c62dd797170b6cdab0c2147d86905f4f49618fdc8748e1335ff6cb040d7e9f1
|
|
BLAKE2b-256 checksum How to use checksums |
2f1ea482f20b5d0c42c46763fc7a53a8bb3020d31d77b6ccc711b942f5d08c24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.5
|
Release files / petal_qc-0.0.34-py3-none-any.whl
| Download URL | petal_qc-0.0.34-py3-none-any.whl |
|---|---|
| Size | 201.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
18067216647359e7dce898fd9e60e6913e1d4f023a995ee6dfb3fac5c371195a
|
|
BLAKE2b-256 checksum How to use checksums |
c6dfb9173b471b58f827d3c44e3c0882a335ba2c2a463a95bb8b2bb4dea13d59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.5
|
Security for petal-qc 0.0.34
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.