1 maintainer
Metadata
1 maintainer
Release files for ctao-bdms-clients 0.11.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 | |
|---|---|---|---|---|
| ctao_bdms_clients-0.11.0.tar.gz | 2.3 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ctao_bdms_clients-0.11.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.4 MB
Release files / ctao_bdms_clients-0.11.0.tar.gz
| Download URL | ctao_bdms_clients-0.11.0.tar.gz |
|---|---|
| Size | 2.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5206773c4277d5a275fc6184b7478cf11c94916bd5c75b30abd4431d14b48485
|
|
BLAKE2b-256 checksum How to use checksums |
ec9ba59e5d62f2dfc04a69d5b5109e036fadf8f4015f5509dc264387eeb9504f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.11
|
Release files / ctao_bdms_clients-0.11.0-py3-none-any.whl
| Download URL | ctao_bdms_clients-0.11.0-py3-none-any.whl |
|---|---|
| Size | 80.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b749e67cc2f2f759cab2aea08ae1c622ac8e8b34544212ccaf4fa4c0c5e6fb98
|
|
BLAKE2b-256 checksum How to use checksums |
8070cf0547e1838f106e17f9060954935d2c204a969476fca541b6ab1a4b5c8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.11
|
Security for ctao-bdms-clients 0.11.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.
