2 maintainers
Metadata
2 maintainers
Release files for hyperetes 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 | |
|---|---|---|---|---|
| hyperetes-0.0.1.tar.gz | 2.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hyperetes-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.2 kB
Release files / hyperetes-0.0.1.tar.gz
| Download URL | hyperetes-0.0.1.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1f4555e2ed40e86940bbf12d83cb4b5296ce5b8712ba14c70a6c8d8f32f168c
|
|
BLAKE2b-256 checksum How to use checksums |
e6d53e1440b1943a6384512e85ca1d59a1475f9df72dcfa4d0a9480c51a559bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / hyperetes-0.0.1-py3-none-any.whl
| Download URL | hyperetes-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
227b627af879f5da00667d4b5048491550b8ca2c4b35a007c73aeceb48ebbf6d
|
|
BLAKE2b-256 checksum How to use checksums |
3d2a6504953feeba4e035480b9bbff55ba0271980b5ae8829bfa46439109230c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for hyperetes 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.
