The author of this package has not provided a project description
Metadata
Release files for pycommon-kit 0.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 | |
|---|---|---|---|---|
| pycommon-kit-0.0.9.tar.gz | 5.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pycommon_kit-0.0.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.1 kB
Release files / pycommon-kit-0.0.9.tar.gz
| Download URL | pycommon-kit-0.0.9.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2387c16f23707c9ea6ffb6a8ae0b5163504038d214688a08e3936c165cd0f7e
|
|
BLAKE2b-256 checksum How to use checksums |
6068ec75de7f2d05093a8d0d25da5154596cd01ee66a5c7b472e95f86ac8d0f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / pycommon_kit-0.0.9-py3-none-any.whl
| Download URL | pycommon_kit-0.0.9-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
794571e7aa70b5ffa5abb04625b7822edd7734b00a675dd5cd4944948893b556
|
|
BLAKE2b-256 checksum How to use checksums |
f2ae544b0f1d4c16c22356689f339cf85324d14d8e401851a110ab12b1cac780
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for pycommon-kit 0.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.