Metadata
Release files for honeypoke-extractor 0.4.3
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 | |
|---|---|---|---|---|
| honeypoke_extractor-0.4.3.tar.gz | 13.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| honeypoke_extractor-0.4.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.4 kB
Release files / honeypoke_extractor-0.4.3.tar.gz
| Download URL | honeypoke_extractor-0.4.3.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2172478b7a1f3fe11edbcb3f3d4e7f8d38caa2e7fb250ccdb39196d4a484d17f
|
|
BLAKE2b-256 checksum How to use checksums |
b064cc420d4eac5fe0934b82be16e0ff3db8964b7f0a82058ad45123cc71779c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / honeypoke_extractor-0.4.3-py3-none-any.whl
| Download URL | honeypoke_extractor-0.4.3-py3-none-any.whl |
|---|---|
| Size | 15.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
36a7baa75faa6ac1a406df1793ef6792f191b385670ccc56d290cd0c971408f9
|
|
BLAKE2b-256 checksum How to use checksums |
2fb6206342bbee5ade601e0a996648ddb49d95a60fe717794420e7729cef3f5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for honeypoke-extractor 0.4.3
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.