Metadata
1 maintainer
Release files for UW-RestClients-PWS 2.1.13
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_pws-2.1.13.tar.gz | 35.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_restclients_pws-2.1.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 132.7 kB
Release files / uw_restclients_pws-2.1.13.tar.gz
| Download URL | uw_restclients_pws-2.1.13.tar.gz |
|---|---|
| Size | 35.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b600ed5a020901bd8a44225f7360cd9e11d43677a3d9d265e3d9ad0f7e321ac7
|
|
BLAKE2b-256 checksum How to use checksums |
d175fd42ed3946f3b3ff5ae53201b01bd55ff26f040e5bf18aef202949b2e03f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.16
|
Release files / uw_restclients_pws-2.1.13-py3-none-any.whl
| Download URL | uw_restclients_pws-2.1.13-py3-none-any.whl |
|---|---|
| Size | 97.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
df172598888f8c2a6c5a08a54054925dd0ccc52cf0e6404ef4bf965980edc5ee
|
|
BLAKE2b-256 checksum How to use checksums |
2b1ccc2b834378e2d8c2d8a8de082cbe1919bc09c660589cff450ff925833bd1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.16
|
Security for UW-RestClients-PWS 2.1.13
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.
