Metadata
Release files for vht-py 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 | |
|---|---|---|---|---|
| vht_py-0.0.1.tar.gz | 17.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vht_py-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 37.3 kB
Release files / vht_py-0.0.1.tar.gz
| Download URL | vht_py-0.0.1.tar.gz |
|---|---|
| Size | 17.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea8c646d3a0f5f69df240f8222cc7683f02468c53f39f21ae4461bf00f519adf
|
|
BLAKE2b-256 checksum How to use checksums |
53d56875ceee7946b6d884cbbf41d14c21f29611a1f6762e4944bc651f7369bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.1.dev0+g94f810c.d20240510 CPython/3.12.5
|
Release files / vht_py-0.0.1-py3-none-any.whl
| Download URL | vht_py-0.0.1-py3-none-any.whl |
|---|---|
| Size | 19.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cad25b0a08620c2f34882d8f077d5d9496544b4f5922c85b543fa54ae04ce5f8
|
|
BLAKE2b-256 checksum How to use checksums |
7e87e9a2aef2989427a148b097524f1e01568fe36dce4af463586a24c3ad15e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.1.dev0+g94f810c.d20240510 CPython/3.12.5
|
Security for vht-py 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.