1 maintainer
Metadata
1 maintainer
Release files for xkits-config-file 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_file-0.9.tar.gz | 3.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xkits_config_file-0.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.0 kB
Release files / xkits_config_file-0.9.tar.gz
| Download URL | xkits_config_file-0.9.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f6ab49074ce7e286e4bde29e328509ce2af2492e3464378ae8ed92cefa01269
|
|
BLAKE2b-256 checksum How to use checksums |
86a0d9910813f0d353af5252621feec6c9739b532d871e180b0552a618b1212b
|
| 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_file-0.9-py3-none-any.whl
| Download URL | xkits_config_file-0.9-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f9fdd0e418d21cdb84989d054119c88b693e035dbbad7a9234322be739631d3
|
|
BLAKE2b-256 checksum How to use checksums |
8142e887440bdda5de81f9b68a97b16440dd50e1f816716ab39ba3ed632edbac
|
| 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-file 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.
