See the README on GitHub.
Metadata
Release files for uw-gcs-clients 1.1.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_gcs_clients-1.1.0.tar.gz | 11.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_gcs_clients-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.8 kB
Release files / uw_gcs_clients-1.1.0.tar.gz
| Download URL | uw_gcs_clients-1.1.0.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
438cd93d170ccbe20695aaa652233351812a087e3b9c2cdeac704013ea2a48ce
|
|
BLAKE2b-256 checksum How to use checksums |
6eba255c2bf72db582259415c5683ef4da2beb53df08320e4a2d5c8541024f48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.20
|
Release files / uw_gcs_clients-1.1.0-py3-none-any.whl
| Download URL | uw_gcs_clients-1.1.0-py3-none-any.whl |
|---|---|
| Size | 13.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dfe4830fa38ab5c4fbffd28cdaea5d1aab04f87185690c94ba7b87d8415ff96d
|
|
BLAKE2b-256 checksum How to use checksums |
9dee383dd5ab340d13f3fb74ff3f0ea06c7ef01691ebed4390e32d82215bdea2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.20
|
Security for uw-gcs-clients 1.1.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.