Metadata
Release files for hull 0.0.1
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 | |
|---|---|---|---|---|
| hull-0.0.1.tar.gz | 1.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hull-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.8 kB
Release files / hull-0.0.1.tar.gz
| Download URL | hull-0.0.1.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a407e6de72bed7c75e78424d6b127a2dbbf0499c68f566181cb8b8682ff2979
|
|
BLAKE2b-256 checksum How to use checksums |
38560e006c9e210e545f51f1ee989841c1663a0ce36c68d4345023e2cfe96d5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.2 CPython/3.9.6
|
Release files / hull-0.0.1-py3-none-any.whl
| Download URL | hull-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f32d5c476614da2f4332a4f8a2522cfa38f3308daaf8b67ee88f8f6ae300883
|
|
BLAKE2b-256 checksum How to use checksums |
a8565e2792c7001a45db434e8e094580d5c76dff3b3378d5c68ac8001fa0b8b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.2 CPython/3.9.6
|
Security for hull 0.0.1
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.