Example Package
This is a simple example package. You can use Github-flavored Markdown to write your content.
1 maintainer
Metadata
1 maintainer
Release files for KuberEnum 1.0.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 | |
|---|---|---|---|---|
| KuberEnum-1.0.1.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| KuberEnum-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.7 kB
Release files / KuberEnum-1.0.1.tar.gz
| Download URL | KuberEnum-1.0.1.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e2b9573f9a5c1b8e02ac2bbe02244c7cccaafa8eb9d03d76515d8f50f67e1da
|
|
BLAKE2b-256 checksum How to use checksums |
65b38c990f898af5ce396ee317e18491f74a77eafa9cc51e14de20a0b59acde6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Release files / KuberEnum-1.0.1-py3-none-any.whl
| Download URL | KuberEnum-1.0.1-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dd0f4e162b71d4375c547c8121adc0a991c4cdbbeccb8753e3b505595b8087ea
|
|
BLAKE2b-256 checksum How to use checksums |
992e7ddf4f3a1e43bbada6b3594929c0aaf6ced12d94d41cb830ff97968a963d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.12
|
Security for KuberEnum 1.0.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.
