See docs at https://kradle.ai/docs/
See how to publish at: https://github.com/Kradle-ai/kradle-python/blob/main/PUBLISHING.md
1 maintainer
Metadata
1 maintainer
Release files for kradle 0.23.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 | |
|---|---|---|---|---|
| kradle-0.23.0.tar.gz | 81.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kradle-0.23.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 167.6 kB
Release files / kradle-0.23.0.tar.gz
| Download URL | kradle-0.23.0.tar.gz |
|---|---|
| Size | 81.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e1eb21e74e3a7679febed39b6ff092cfc873cfebb9561c24778f391f1732b000
|
|
BLAKE2b-256 checksum How to use checksums |
eb68ff5ea648bd5a003f2834a3abf4bde1d6706b9a6bb3da9ccdb58f60b3d719
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / kradle-0.23.0-py3-none-any.whl
| Download URL | kradle-0.23.0-py3-none-any.whl |
|---|---|
| Size | 86.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0cfb002e3a36a7062bf6eea34048870f451961d46a4197ebe2b3d6505dedc3ff
|
|
BLAKE2b-256 checksum How to use checksums |
eaaafa23e821cad38822469ee5a2241978ef7ad7e98d08468db91d4497b01f2c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Security for kradle 0.23.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.
