[vovapi]

Plugin Submission

Plugin information

• Author: vovapi
• Plugin name: docling_remote (Docling Remote)
• Version: 0.1.4
• Source repository: https://github.com/vovapi/dify-docling-remote
• Contact: evgrafov.vladimir@gmail.com; support: https://github.com/vovapi/dify-docling-remote/issues

Submission type

• New plugin
• Version update

What changed

Docling Remote connects Dify to an administrator-operated Docling Serve. It provides server health checks and conversion of 1–10 uploaded documents with OCR, table extraction, five export formats, ZIP output, and optional hierarchical/hybrid chunking that reuses Docling JSON without repeating OCR.

The existing s20ss/docling integration embeds the Docling conversion stack. This plugin addresses separately deployed Serve installations: its runtime contains no Docling, Torch, model weights, shell execution or conversion subprocesses. Server models, hardware and deployment remain under the administrator's control. The 0.1.4 package updates release metadata and documentation links for Marketplace; conversion behavior is unchanged from 0.1.3.

Risk level

• Low risk
• Medium risk
• High risk

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
• The package contains only files needed at runtime.
• The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
• The package does not contain executables or bundled binaries, or I explained why they are required below.
• The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md or a hosted privacy policy, and manifest.yaml references it.
• All user-facing text is primarily in English, with any localized README files following the i18n guidance.

Security and privacy notes

High risk is selected conservatively because arbitrary uploaded documents can contain health, financial or other sensitive personal data. Document bytes, filenames and conversion options are sent to the administrator-configured HTTP(S) Serve endpoint; an optional API key is sent as X-Api-Key. Only provider administrators choose the URL; workflow inputs cannot override it. Private network destinations are supported intentionally. Redirects and environment proxies are disabled, TLS verification is enabled. The Dify SDK retrieves uploaded files from Dify storage. No general URL-fetching tool, proxy, shell/code execution, SQL, SSH/SFTP or browser automation is exposed.

Processing and ZIP creation occur in memory; the plugin does not persist document content to its own filesystem. Dify and Serve may retain inputs/results according to their configurations. The developer operates no collection or analytics service. Raw server error bodies, signed file URLs and credentials are suppressed in diagnostics. Input count/size and response/result sizes are bounded. Per-document deadlines are configurable; timeouts do not cancel server tasks. Administrators must use a trusted Serve instance and HTTPS across untrusted networks.

Local validation

• Python 3.12.14, frozen uv sync: passed.
• uv run pytest -q: 38 passed; two existing SDK/dependency warnings.
• Frozen runtime requirements export matches requirements.txt.
• Official Dify CLI 0.6.11, scripts/package.py runtime allowlist: built successfully.
• Marketplace Toolkit 57a21d1304b1108df3e6b90a15a4f5dd9f0915f9: passed, exit 0, no blocking failures or execution failures. Online dependency lookup reported no known vulnerabilities in the pinned set.
• Validation command: PATH=/private/tmp/docling-publish-tools/bin:$PATH .venv/bin/python /private/tmp/docling-marketplace-toolkit/validator/validate-difypkg.py dist/docling-remote-0.1.4.difypkg --output-dir .cache/marketplace-validation-final --pr-body-file .cache/marketplace-pr.md
• Package SHA-256: 165890f09b7e0fb8036470f2ea774b4b1d377ac8735b4a3f418ee8e04176da2c.

Reviewer notes

Previously verified with Dify 1.17.1, native Linux arm64 runtime and Docling Serve 1.21.0: multilingual HTML, scanned PDFs, multiple exports, hierarchical chunking and batch conversion. Version 0.1.3 also completed a three-PDF run in a Kubernetes Dify workspace. Version 0.1.4 changes metadata/documentation only; no fresh Serve/Dify integration run is claimed.

Dify Cloud connectivity, native amd64, CUDA, VLM/enrichment inference and full-scale load have not been verified. Inline text/JSON is bounded; full exports are retained in ZIP. OCR may contain errors. An optional Compose example is supplied in the source repository but has not been integration-tested.

Static scan notes: tiktoken in requirements.txt is a dependency name, not a secret; max_tokens in engine/options.py is a chunk-size parameter, not a credential. No minimum Dify version is claimed: 1.17.1 is the tested baseline, not an established minimum. No Marketplace approval is claimed.