1 maintainer
Metadata
1 maintainer
Release files for click-expand 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 | |
|---|---|---|---|---|
| click_expand-0.1.0.tar.gz | 4.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| click_expand-0.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 8.5 kB
Release files / click_expand-0.1.0.tar.gz
| Download URL | click_expand-0.1.0.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
55045bbe987e2a18ae66cea0352e94c4d1847a9833c902cc9178b68015c25758
|
|
BLAKE2b-256 checksum How to use checksums |
32e087abb004d6995b8937a240a135959f11023675b4bc2216d3f37941fedac4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Release files / click_expand-0.1.0-py2.py3-none-any.whl
| Download URL | click_expand-0.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
c5a2b56399fa1b525ad428457ee0667474c00c1805761e6b1a10ece5617d8d29
|
|
BLAKE2b-256 checksum How to use checksums |
164f60e285570719d564dba8779815e1501633ae5d773f19ed9587be772f32c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for click-expand 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.
