The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for clickstate 0.0.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 | |
|---|---|---|---|---|
| clickstate-0.0.1.tar.gz | 475 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| clickstate-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.5 kB
Release files / clickstate-0.0.1.tar.gz
| Download URL | clickstate-0.0.1.tar.gz |
|---|---|
| Size | 475 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dab56fbc0b85f288c1de3f4a7d1e43aff28de4d971adbbc4731e8448e99277ce
|
|
BLAKE2b-256 checksum How to use checksums |
c9f07be07b2ebe26ddac296bd79bcd52e557f6968787e098c60dcfd4ccccc7e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / clickstate-0.0.1-py3-none-any.whl
| Download URL | clickstate-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b21710e883029898f566817f21176c7ff3dd719ab54170fbc9b33506644793a
|
|
BLAKE2b-256 checksum How to use checksums |
7e5ba4acd14c3b56ce0df511e98b11fe682e7917c37953277271894701bd6e6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for clickstate 0.0.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.
