The author of this package has not provided a project description
Metadata
Release files for cliff-agent 0.1.1
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 | |
|---|---|---|---|---|
| cliff_agent-0.1.1.tar.gz | 13.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cliff_agent-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.9 kB
Release files / cliff_agent-0.1.1.tar.gz
| Download URL | cliff_agent-0.1.1.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1fff0b0c9899d44799786770155906cfb28bb875a0b8345a4d6da4247b63be23
|
|
BLAKE2b-256 checksum How to use checksums |
a366dafa23a5d7ad9bc7737d9102810acea2eecd4d7149f5f3a6258931730cc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Release files / cliff_agent-0.1.1-py3-none-any.whl
| Download URL | cliff_agent-0.1.1-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cde161bdddd08900a4291dcfea90bcf4d12c1129752b3cff6be1a9284d79f072
|
|
BLAKE2b-256 checksum How to use checksums |
f181d580e0c0dfc641961a255f75da7e292017fa51c254546ed2360791f504fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Security for cliff-agent 0.1.1
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.