This release is a pre-release and may not be stable for production use.
1 maintainer
Metadata
1 maintainer
Release files for kadm 0.1a1
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 | |
|---|---|---|---|---|
| kadm-0.1a1.tar.gz | 9.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kadm-0.1a1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 19.0 kB
Release files / kadm-0.1a1.tar.gz
| Download URL | kadm-0.1a1.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ddeef87652fb3c7018d3a7da0c655938a893e642f185aab757b1870dd9ae947
|
|
BLAKE2b-256 checksum How to use checksums |
6d03cc5bddedd2937c794e2cfc235318fe5bfead08cbd79b6be15a734494e0ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.21
|
Release files / kadm-0.1a1-py2.py3-none-any.whl
| Download URL | kadm-0.1a1-py2.py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
1f518249127f005ee1fdb197c9258fd65a354fc446f0203ad0bc630214c0e248
|
|
BLAKE2b-256 checksum How to use checksums |
5e62e47a1319944a654ea53f021df8d506d1beea266fcf7ea14667d537b648bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.21
|
Security for kadm 0.1a1
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.
