2 maintainers
Metadata
2 maintainers
Release files for kape-extractor 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 | |
|---|---|---|---|---|
| kape_extractor-0.0.0.tar.gz | 745 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kape_extractor-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.1 kB
Release files / kape_extractor-0.0.0.tar.gz
| Download URL | kape_extractor-0.0.0.tar.gz |
|---|---|
| Size | 745 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa23f980814afcd9c97029369286d6bf3f14d37c9925a66070931f4f00e56a3b
|
|
BLAKE2b-256 checksum How to use checksums |
e2f433c20c47d51ef53d652b2c2e887ba0a74a2cbe58c5e9b5ea66324648b60e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / kape_extractor-0.0.0-py3-none-any.whl
| Download URL | kape_extractor-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
05811903b01ef71934ddbb120c15905ad813631ac9e45db2f9f9401cb785a009
|
|
BLAKE2b-256 checksum How to use checksums |
47af98743a88a1a270915e20f9cfb171f76a02c78313a6236431cdd091fa8839
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for kape-extractor 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.
