The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for hypergo 0.3.19
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 | |
|---|---|---|---|---|
| hypergo-0.3.19.tar.gz | 42.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hypergo-0.3.19-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.3 kB
Release files / hypergo-0.3.19.tar.gz
| Download URL | hypergo-0.3.19.tar.gz |
|---|---|
| Size | 42.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7eaf30aaf294afc84ad730d49294f3394b3a35e6d96efef4e89afadc5704bbd9
|
|
BLAKE2b-256 checksum How to use checksums |
44ad37cbe7071f4782248d37bf69bb904c557645b93e56756e27dbbf6c688e66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.19
|
Release files / hypergo-0.3.19-py3-none-any.whl
| Download URL | hypergo-0.3.19-py3-none-any.whl |
|---|---|
| Size | 32.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
41cdf5a37abce8f8a5de34a945b43f5d2b3820d2de478b76d9c90d1b139c3cee
|
|
BLAKE2b-256 checksum How to use checksums |
72e15fe1ce1f0146f025866b55aa172f53b8b4e67693608bb8373b14ecc21e45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.9.19
|
Security for hypergo 0.3.19
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.
