The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for kcp-wrapper 0.2.18
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 | |
|---|---|---|---|---|
| kcp_wrapper-0.2.18.tar.gz | 123.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kcp_wrapper-0.2.18-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 247.5 kB
Release files / kcp_wrapper-0.2.18.tar.gz
| Download URL | kcp_wrapper-0.2.18.tar.gz |
|---|---|
| Size | 123.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cedc6227b8b1dbeb3a11f8c75113fb179fa6509d6db92d491d0a8245ad0eef92
|
|
BLAKE2b-256 checksum How to use checksums |
6f318f95b5125bc40283591d4dc1a79681fe59c70444030b4e591ab5f68d093a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / kcp_wrapper-0.2.18-py3-none-any.whl
| Download URL | kcp_wrapper-0.2.18-py3-none-any.whl |
|---|---|
| Size | 123.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8cd2460d94c4bc2f20b826da11e98aef3d326170a78f7f888e34220293439b9
|
|
BLAKE2b-256 checksum How to use checksums |
1eb738f25eb8319e109f6ef31ccb38a471286196e6036edb3c3ee9bf89eb5067
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for kcp-wrapper 0.2.18
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.
