Fetch, Upload, Organize, and Distribute Software Packages # noqa: E501
Metadata
Release files for pulpcore-client 3.22.20
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 | |
|---|---|---|---|---|
| pulpcore-client-3.22.20.tar.gz | 132.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pulpcore_client-3.22.20-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 459.6 kB
Release files / pulpcore-client-3.22.20.tar.gz
| Download URL | pulpcore-client-3.22.20.tar.gz |
|---|---|
| Size | 132.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c2af4fa6539aba0f841e4f6551071e2c4e54ea605dfd92afe80c8b5b20c91d6
|
|
BLAKE2b-256 checksum How to use checksums |
51b9bd74eecac2fe236e3709e16eb7d7c6b1f038ecde54f8cc6cbdf930ef19b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.18
|
Release files / pulpcore_client-3.22.20-py3-none-any.whl
| Download URL | pulpcore_client-3.22.20-py3-none-any.whl |
|---|---|
| Size | 326.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0962a5d3e566f4672e501244d224cf7b7fb7eca56d06fd52cdf527d45fa646db
|
|
BLAKE2b-256 checksum How to use checksums |
e463a5690bf43e3b83b9b1bbb11a18112cecd49a738670c877ca5108bd06388a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.18
|
Security for pulpcore-client 3.22.20
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.