1 maintainer
Metadata
1 maintainer
Release files for ocr-indexer-pro 0.4.12
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 | |
|---|---|---|---|---|
| ocr_indexer_pro-0.4.12.tar.gz | 30.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ocr_indexer_pro-0.4.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 65.0 kB
Release files / ocr_indexer_pro-0.4.12.tar.gz
| Download URL | ocr_indexer_pro-0.4.12.tar.gz |
|---|---|
| Size | 30.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1855bf550a9b729c19e0ace97f2b55d49ab4dd9d0342a71b345b02555c1ed20c
|
|
BLAKE2b-256 checksum How to use checksums |
4a3656858dcddc5ec363c64ffb034b378923ef7a6eee55885afcf29e88b556cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / ocr_indexer_pro-0.4.12-py3-none-any.whl
| Download URL | ocr_indexer_pro-0.4.12-py3-none-any.whl |
|---|---|
| Size | 34.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c71e7ed9341c1c2c997e83d335f0dbddb284c1c65c58616d65416d9dbfd09534
|
|
BLAKE2b-256 checksum How to use checksums |
1457585b1665c21ffe53b71b112190f4d0fcfcdef4e569555f5a1420df21d7ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for ocr-indexer-pro 0.4.12
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.
