1 maintainer
Metadata
1 maintainer
Release files for aquahawk-client 0.0.5
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 | |
|---|---|---|---|---|
| aquahawk_client-0.0.5.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aquahawk_client-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.3 kB
Release files / aquahawk_client-0.0.5.tar.gz
| Download URL | aquahawk_client-0.0.5.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c4f32a06737829cfce5dd2b629c7e9971cdfdb1eac23b5ee688e6536b93ffe6f
|
|
BLAKE2b-256 checksum How to use checksums |
cf4a0a77348320a6fb318c0327c6efddf982d120a9c5d7dff8bcc504392048f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.8
|
Release files / aquahawk_client-0.0.5-py3-none-any.whl
| Download URL | aquahawk_client-0.0.5-py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e3794e040aeb0580bb4b7f1a06b3074b9d9f85eacef51d4e5e8abf6d5470921
|
|
BLAKE2b-256 checksum How to use checksums |
3540065693c045cc38a6f3d20154090459e0c59586c1ede65eef1b8aaf2e315c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.8
|
Security for aquahawk-client 0.0.5
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.
