Metadata
1 maintainer
Release files for UW-RestClients-KWS 1.1.3
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_kws-1.1.3.tar.gz | 8.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_restclients_kws-1.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.3 kB
Release files / uw_restclients_kws-1.1.3.tar.gz
| Download URL | uw_restclients_kws-1.1.3.tar.gz |
|---|---|
| Size | 8.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fee7c6b994756a5c6d3c1d2e86b8b7d5fd6bce7d337d57c689e1030353aa7dd1
|
|
BLAKE2b-256 checksum How to use checksums |
8ab50d623075b030b431734c73accde5501a1d62ca80b64dd86d76326ca7b005
|
| 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_kws-1.1.3-py3-none-any.whl
| Download URL | uw_restclients_kws-1.1.3-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
02353c8999d21864111fdc5ccef2d59e49ca03fea7000641ff7cac31cf48dba3
|
|
BLAKE2b-256 checksum How to use checksums |
cd22e33dc4b962beddd39491f207fdc97431a093dc536faf10cdfbae6d7f3a9e
|
| 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-KWS 1.1.3
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.
