Metadata
1 maintainer
Release files for UW-RestClients-HRP 1.3.5
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 | |
|---|---|---|---|---|
| uw_restclients_hrp-1.3.5.tar.gz | 38.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_restclients_hrp-1.3.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 98.6 kB
Release files / uw_restclients_hrp-1.3.5.tar.gz
| Download URL | uw_restclients_hrp-1.3.5.tar.gz |
|---|---|
| Size | 38.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a0b5cc094bc7742f2883b7b55151c68fb9384b6a08eaef946f3fae0545320219
|
|
BLAKE2b-256 checksum How to use checksums |
b43ce546a9ccc4b2d025f0ae35e613bd365ace9cbd27aa9ddd5ec5730553144b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Release files / uw_restclients_hrp-1.3.5-py3-none-any.whl
| Download URL | uw_restclients_hrp-1.3.5-py3-none-any.whl |
|---|---|
| Size | 60.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
39c4a2609f2729da3a6701e5dfda28aa5e8ed8987061ef73c86d694d93b6ec31
|
|
BLAKE2b-256 checksum How to use checksums |
d38121741fadf5c11dc3a32002d394d7f3dae8c9e6113a672fc2dd6da69d52b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Security for UW-RestClients-HRP 1.3.5
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.
