DeepRead OCR
PassAudited by ClawScan on May 1, 2026.
Overview
DeepRead OCR is a coherent instruction-only integration, but it sends user documents to DeepRead with an API key and can deliver results by webhook, so sensitive documents and credentials should be handled carefully.
This skill appears purpose-aligned and instruction-only. Before using it, confirm you are comfortable sending the selected documents to DeepRead, keep DEEPREAD_API_KEY out of files and chat logs, secure any webhook endpoint, and verify the provider/release metadata if strict provenance matters to you.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone with access to the configured key may be able to use the DeepRead account quota or submit documents under that account.
The skill explicitly requires a DeepRead API key. This is expected for the OCR service, but it is still an account credential that can authorize document-processing requests.
"requires":{"env":["DEEPREAD_API_KEY"]},"primaryEnv":"DEEPREAD_API_KEY"Store the key only in the environment, do not commit it to configuration files, rotate it if exposed, and use the least-privileged key settings available from the provider.
Private documents and extracted text may be processed by the provider and delivered to the configured webhook endpoint.
The documented workflow uploads user documents to DeepRead and can send results to a user-provided webhook. This is purpose-aligned for OCR, but it is a sensitive external data flow.
curl -X POST https://api.deepread.tech/v1/process ... -F "file=@document.pdf" ... -F "webhook_url=https://your-app.com/webhooks/deepread"
Use this only for documents you are allowed to send to DeepRead, secure webhook endpoints with HTTPS and authentication or signature verification where available, and avoid sending unnecessary sensitive data.
It may be harder to confirm that the registry entry and packaged files refer to the same release.
The supplied registry metadata lists version 1.1.0, while package.json and _meta.json list 1.0.6. This does not indicate harmful behavior, but it makes artifact/version provenance less tidy.
"version": "1.0.6"
Publisher should align registry, package.json, and _meta.json versions; users who care about provenance should verify the homepage or repository before installing.