Metadata
1 maintainer
Release files for UW-RestClients-UPass 4.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 | |
|---|---|---|---|---|
| uw_restclients_upass-4.0.tar.gz | 9.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_restclients_upass-4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.9 kB
Release files / uw_restclients_upass-4.0.tar.gz
| Download URL | uw_restclients_upass-4.0.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
92ca308a59b09b964b816564a7034f79127e60abe37b075e47d25f427a8008cb
|
|
BLAKE2b-256 checksum How to use checksums |
c2ebe575de368ca53f876e98377fed0cc0293712ecc54ae5369042b7b0892116
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / uw_restclients_upass-4.0-py3-none-any.whl
| Download URL | uw_restclients_upass-4.0-py3-none-any.whl |
|---|---|
| Size | 13.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3af5ce52108690fe820864aa29a74a3e2ecdfd69893b8aee62be522d815b112
|
|
BLAKE2b-256 checksum How to use checksums |
858864a207b794abdd384f477b4c4e55bbf6260fac16fe5e32fd6e180a2ddedb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for UW-RestClients-UPass 4.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.
