The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for cladia 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 | |
|---|---|---|---|---|
| cladia-0.1.0.tar.gz | 550 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cladia-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / cladia-0.1.0.tar.gz
| Download URL | cladia-0.1.0.tar.gz |
|---|---|
| Size | 550 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd3b04c38f51f8a5acb52f546f036f5a6a8ffcd355149132f038137f1381e1d7
|
|
BLAKE2b-256 checksum How to use checksums |
6ca8700c1a269984ea3b51ef9411e6ffda26da2ee74ba58532b3010c2a9fc5f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / cladia-0.1.0-py3-none-any.whl
| Download URL | cladia-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7039797c2042cec81a5a54d256849ccc9a737eff16ee19311a2ff3d0af5b8f98
|
|
BLAKE2b-256 checksum How to use checksums |
27e85c864860a7b0f6008b3b54a78fe5d89254dd64f604e4cec1183017f50b95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for cladia 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.
