Metadata
1 maintainer
Release files for UW-RestClients-HFS 1.0.7
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_hfs-1.0.7.tar.gz | 10.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uw_restclients_hfs-1.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.4 kB
Release files / uw_restclients_hfs-1.0.7.tar.gz
| Download URL | uw_restclients_hfs-1.0.7.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93544872f1272ba4c600d3c84606f7f704b7ba70d3fbc346bc7187b1522f5c8b
|
|
BLAKE2b-256 checksum How to use checksums |
f03b85c3e6212a211807e29ad4d28162179c1c6817f837fd9d2ddee0e2f71984
|
| 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_hfs-1.0.7-py3-none-any.whl
| Download URL | uw_restclients_hfs-1.0.7-py3-none-any.whl |
|---|---|
| Size | 14.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f9dd3bfbca156e599ef73ee57f3e2eda3e5be0dc1c659bafa8a16ace46e107a
|
|
BLAKE2b-256 checksum How to use checksums |
e416d631bb1e7f41a19ec7c544876f3d3673ef7b60da419f179cf448f7aa0f4a
|
| 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-HFS 1.0.7
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.
