Metadata
1 maintainer
Release files for UW-RestClients-R25 0.6
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_r25-0.6.tar.gz | 11.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_restclients_r25-0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.1 kB
Release files / uw_restclients_r25-0.6.tar.gz
| Download URL | uw_restclients_r25-0.6.tar.gz |
|---|---|
| Size | 11.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3399a85db9342f3551308b826252189af1ab5e27801493e6e4f09ea30386dd3e
|
|
BLAKE2b-256 checksum How to use checksums |
1986fd87d7ea1642ab9712b5bb2462ce9e0bb2c86aa545ae10cc55dc21849728
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Release files / uw_restclients_r25-0.6-py3-none-any.whl
| Download URL | uw_restclients_r25-0.6-py3-none-any.whl |
|---|---|
| Size | 18.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cfc5a7a7d39dd70b52a70dd8e904eb170d2e90c1f3dfccbd8d501b2fb7c6f5c6
|
|
BLAKE2b-256 checksum How to use checksums |
d98ec083c92bb5f6ab6efc70fa10e8a40aa7ce858ca5d9dc5d4c1a68dd2a2f45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Security for UW-RestClients-R25 0.6
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.
