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