1 maintainer
Metadata
1 maintainer
Release files for xkits-config-yaml 0.9
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 | |
|---|---|---|---|---|
| xkits_config_yaml-0.9.tar.gz | 3.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xkits_config_yaml-0.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.6 kB
Release files / xkits_config_yaml-0.9.tar.gz
| Download URL | xkits_config_yaml-0.9.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1cd78a554346fd662ab1e3fb010e41c6957ca784052a14825c356f38d67733c0
|
|
BLAKE2b-256 checksum How to use checksums |
283dc630994c4949e4f7263b22dc6ba5238e6ec09bce2ab56ba7e8fb100047ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / xkits_config_yaml-0.9-py3-none-any.whl
| Download URL | xkits_config_yaml-0.9-py3-none-any.whl |
|---|---|
| Size | 8.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
29d4caaf01cbc0911f55bdeaf5df803a122176c0088bf7b54625e241c0de881c
|
|
BLAKE2b-256 checksum How to use checksums |
7870e291a015d832f9c6701111813ae70f6a2ec55668a9bbad3ed963f7faa266
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for xkits-config-yaml 0.9
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.
