The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for nimocr 0.1.2
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 | |
|---|---|---|---|---|
| nimocr-0.1.2.tar.gz | 8.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nimocr-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.3 kB
Release files / nimocr-0.1.2.tar.gz
| Download URL | nimocr-0.1.2.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
39ef3a58b746ba612d7ff0ea5f57bfab71c18ad8a77bd12d7b9409cea411b5b6
|
|
BLAKE2b-256 checksum How to use checksums |
c6124113d89a17b0b8f45b0f4ace15764942b8793e2dc152431746eb40016786
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / nimocr-0.1.2-py3-none-any.whl
| Download URL | nimocr-0.1.2-py3-none-any.whl |
|---|---|
| Size | 10.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
39b6d989109deee39a0c0a101f78f33173af09c4d2605f073ab7211a00a4056d
|
|
BLAKE2b-256 checksum How to use checksums |
84fd316df2fd3b316fa7223d63424dc3e9d961555c3356fb8020c9453677d6d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for nimocr 0.1.2
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.
