The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for paddleocr-mcp 0.8.5
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 | |
|---|---|---|---|---|
| paddleocr_mcp-0.8.5.tar.gz | 20.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| paddleocr_mcp-0.8.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 71.1 kB
Release files / paddleocr_mcp-0.8.5.tar.gz
| Download URL | paddleocr_mcp-0.8.5.tar.gz |
|---|---|
| Size | 20.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcf99dd7dd6a01a6906dfe8213181c7f12990e8ca8e1fc32a3d1971237e92a8b
|
|
BLAKE2b-256 checksum How to use checksums |
09557ea8c9244df8c944e0b09cc539c96d7204da6dbc0884f2f97710e18a25d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Release files / paddleocr_mcp-0.8.5-py3-none-any.whl
| Download URL | paddleocr_mcp-0.8.5-py3-none-any.whl |
|---|---|
| Size | 50.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be36b448d1e615f77a3e63c38adf91ccca68cc3f381da20aded6a4031e8b3e61
|
|
BLAKE2b-256 checksum How to use checksums |
a381b120ce8c11d1174d6544f5c862c076f09a81505f0bce06c39069ae6d6ac2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Security for paddleocr-mcp 0.8.5
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.
