1 maintainer
Metadata
1 maintainer
Release files for izihawa-configurator 1.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 | |
|---|---|---|---|---|
| izihawa_configurator-1.1.0.tar.gz | 6.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| izihawa_configurator-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.2 kB
Release files / izihawa_configurator-1.1.0.tar.gz
| Download URL | izihawa_configurator-1.1.0.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd192bcef973f2c42eee9ad1e301a0326fc04540552e23b1b24c903f2bda756b
|
|
BLAKE2b-256 checksum How to use checksums |
2738502c108f62087984df5074cc43ab466fe2cf9f1a839e43e107f4833b77df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / izihawa_configurator-1.1.0-py3-none-any.whl
| Download URL | izihawa_configurator-1.1.0-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4cbe725ef24bc3b1a7d2ae513d34c89cd4778a6abe479545d088a7731e833163
|
|
BLAKE2b-256 checksum How to use checksums |
a63c59d939432cbcd120e8e7fdcfc82b38f5e4d877da2f84ca4265750b8aeafd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for izihawa-configurator 1.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.
