Metadata
1 maintainer
Release files for UW-RestClients-CoDa 1.0.4
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_coda-1.0.4.tar.gz | 7.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_restclients_coda-1.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.8 kB
Release files / uw_restclients_coda-1.0.4.tar.gz
| Download URL | uw_restclients_coda-1.0.4.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a8c5e4bbd4a3dcd7b63b355a516632a06c718e87aed7689e476ecea44365b1dc
|
|
BLAKE2b-256 checksum How to use checksums |
034f7806b18e724dc7b88a7d523760e2ad4081c9efad2ba916177e65eb1b0e28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Release files / uw_restclients_coda-1.0.4-py3-none-any.whl
| Download URL | uw_restclients_coda-1.0.4-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44ecfc5ae6523296075d12b1afb3495526fa85cb4bd5d1584ac4e54107b8fafa
|
|
BLAKE2b-256 checksum How to use checksums |
d98e9afcb7db52a5df269f5f277bef867f24c545d2cdfdf1c091f24f946cbda1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for UW-RestClients-CoDa 1.0.4
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.
