The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for kbckit 0.1.0
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 | |
|---|---|---|---|---|
| kbckit-0.1.0.tar.gz | 2.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kbckit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.9 kB
Release files / kbckit-0.1.0.tar.gz
| Download URL | kbckit-0.1.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17d035e881d8a561202548a249bc0ca79295e98b684f10799e5fb98221511c7a
|
|
BLAKE2b-256 checksum How to use checksums |
ce12576c44140fe847a6e833f3b2bfb8f817add39c71ffc3d19aafecaee983e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.5 CPython/3.6.6 Windows/10
|
Release files / kbckit-0.1.0-py3-none-any.whl
| Download URL | kbckit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84f6057fa28a6aa4ee13615bffe45b06ac91463050c0030d75adce902b7c22e6
|
|
BLAKE2b-256 checksum How to use checksums |
647fc1065cd43e39c411b164b85a922e823f966476d5841e916003c162ee29e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/0.12.5 CPython/3.6.6 Windows/10
|
Security for kbckit 0.1.0
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.
