1 maintainer
Metadata
1 maintainer
Release files for compress-anything 0.0.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 | |
|---|---|---|---|---|
| compress_anything-0.0.0.tar.gz | 2.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| compress_anything-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.4 kB
Release files / compress_anything-0.0.0.tar.gz
| Download URL | compress_anything-0.0.0.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37957d95a0fd528cbcda5127d374732aaedd39f452d75bb3e7afd1a33961a19d
|
|
BLAKE2b-256 checksum How to use checksums |
3455967df598f003bd836b52cb8f1bb10812e1fe7ba6c4f532ed6a33fef16112
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Release files / compress_anything-0.0.0-py3-none-any.whl
| Download URL | compress_anything-0.0.0-py3-none-any.whl |
|---|---|
| Size | 2.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3255250255bca563ec12c5b95c31a14f6ddf1a8d85e3c52824fc8063f2b6c9b
|
|
BLAKE2b-256 checksum How to use checksums |
10cd824b1b26ba2f43349e0dd2496f9abaf9666e26c3b593e7063c0ca22f168c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for compress-anything 0.0.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.
