1 maintainer
Metadata
1 maintainer
Release files for np-pipeline-qc 0.0.30
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 | |
|---|---|---|---|---|
| np-pipeline-qc-0.0.30.tar.gz | 2.0 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| np_pipeline_qc-0.0.30-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.7 MB
Release files / np-pipeline-qc-0.0.30.tar.gz
| Download URL | np-pipeline-qc-0.0.30.tar.gz |
|---|---|
| Size | 2.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a784a1640c8d3d6ecfd275c13b8e6d96405386d93656c52597c696a488d6bf99
|
|
BLAKE2b-256 checksum How to use checksums |
60307fa761212c94cf03ae58f4b058c028ec09b240df4fec94975d9a56a685d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.7.4 CPython/3.8.10
|
Release files / np_pipeline_qc-0.0.30-py3-none-any.whl
| Download URL | np_pipeline_qc-0.0.30-py3-none-any.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d2e6a7c48624bd862649a5c7f5d77a69a214cf659434c817b182e36ebad7fb50
|
|
BLAKE2b-256 checksum How to use checksums |
2c5abed14bb3a85bafce6badc1ad529f8b5112682fc5cd8a60e566ab6b826abf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.7.4 CPython/3.8.10
|
Security for np-pipeline-qc 0.0.30
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.
