The author of this package has not provided a project description
Metadata
Release files for madhack-cli 0.1.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 | |
|---|---|---|---|---|
| madhack_cli-0.1.1.tar.gz | 17.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| madhack_cli-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 59.8 kB
Release files / madhack_cli-0.1.1.tar.gz
| Download URL | madhack_cli-0.1.1.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c3ff6409911e8ef5b93e60e3daaf9fff103213e21c160d703a538ab53018d67
|
|
BLAKE2b-256 checksum How to use checksums |
25b315e20c0df24e6f2eb0fb02d3fa002b93429b5f37c6e3eed96296b7c8f205
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / madhack_cli-0.1.1-py3-none-any.whl
| Download URL | madhack_cli-0.1.1-py3-none-any.whl |
|---|---|
| Size | 42.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f98279a7f1fe37d637e9f20cf4099779ee343e4a25a3a86851e73a8ea3bfb3dc
|
|
BLAKE2b-256 checksum How to use checksums |
0b2804e52e4947a2fb3f7c271e3662ad255fa1384a995a71e3c8e67d7a8f8d16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for madhack-cli 0.1.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.