Metadata
1 maintainer
Release files for UW-RestClients-MSCA 0.2.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_msca-0.2.3.tar.gz | 17.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_restclients_msca-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.7 kB
Release files / uw_restclients_msca-0.2.3.tar.gz
| Download URL | uw_restclients_msca-0.2.3.tar.gz |
|---|---|
| Size | 17.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
96e943b7a8b12b4dd034af5eca788dd5b8dd47d774ad8439879dbc070444f574
|
|
BLAKE2b-256 checksum How to use checksums |
1282cccaf292ba228a8ea3e4dd07abaaec50a9becfc980bed876ca4a3e8c8596
|
| 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_msca-0.2.3-py3-none-any.whl
| Download URL | uw_restclients_msca-0.2.3-py3-none-any.whl |
|---|---|
| Size | 27.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
944f684b9a86a6e373b62cffe24148ef3613e8501fa707d2b79ff1d17fdaa8ea
|
|
BLAKE2b-256 checksum How to use checksums |
f2c6e7eb59fc5cfababb74c389f532377a2461e738d8026ca36f75386bb9b376
|
| 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-MSCA 0.2.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.
