The author of this package has not provided a project description
Metadata
Release files for minectl 0.1.0
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 | |
|---|---|---|---|---|
| minectl-0.1.0.tar.gz | 4.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| minectl-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.4 kB
Release files / minectl-0.1.0.tar.gz
| Download URL | minectl-0.1.0.tar.gz |
|---|---|
| Size | 4.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eba6cade8a99811749b1fa3b329d6d8fec862a0ac19d3bbe12068a1d4ca37c9f
|
|
BLAKE2b-256 checksum How to use checksums |
fb91ac741ac1498a90e9be5ee521cfeae4b9076471c876bd0ba0ad2fc59ad206
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.11 CPython/3.9.7 Linux/5.13.19-2-MANJARO
|
Release files / minectl-0.1.0-py3-none-any.whl
| Download URL | minectl-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
041b5fd80dd4376fcc5ebd862d4e258c3ecd209ff2d450202b39a49be30e73a2
|
|
BLAKE2b-256 checksum How to use checksums |
36db9701f0d78ea9f9aefa1653996a3bfc55bea887843e9a8518f4570ac9a60c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.11 CPython/3.9.7 Linux/5.13.19-2-MANJARO
|
Security for minectl 0.1.0
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.