The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for hyperdrone 0.1.4
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 | |
|---|---|---|---|---|
| hyperdrone-0.1.4.tar.gz | 1.1 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hyperdrone-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 MB
Release files / hyperdrone-0.1.4.tar.gz
| Download URL | hyperdrone-0.1.4.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
202d9fbc2e40d59d2064551ff07db29f60be8a55915bd9f0569ae8461fdfca29
|
|
BLAKE2b-256 checksum How to use checksums |
05641ac0749da92b0489c4cca4f67bcf9ebc3ec77f51c269dd8e5ce7d9d6fda3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.8
|
Release files / hyperdrone-0.1.4-py3-none-any.whl
| Download URL | hyperdrone-0.1.4-py3-none-any.whl |
|---|---|
| Size | 1.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
493ecf3755b6f52ffa90655e26c44c8ab3d930885d88fc0682669ac72bc98ea0
|
|
BLAKE2b-256 checksum How to use checksums |
54cf0963e51c823505b6a8bfdbd268a713700248f1215f0aab890c4aebdc61a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.8
|
Security for hyperdrone 0.1.4
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.
