Update plugin: enconvert/enconvert v0.0.2

[OmJadav9]

Plugin Submission

Plugin information

• Author: enconvert
• Plugin name: enconvert
• Version: 0.0.2
• Source repository: https://github.com/enconvert/dify-enconvert
• Contact: support@enconvert.com

Submission type

• New plugin
• Version update

What changed

Version update from 0.0.1 (merged in #2999) to 0.0.2. One behavioural change, in the Perceive URL tool only.

The EnConvert API returns a detected content-free block (an anti-bot challenge or an empty app shell) as a normal success with is_blocked true and empty outputs, and does not bill it. In 0.0.1 the tool's text summary reported only the render quality and the list of outputs, so an agent could read a blocked page's summary as a successful read. In 0.0.2 the summary states explicitly that the page was blocked and must not be treated as content, and notes when the read was not billed. The JSON message returned by the tool is unchanged.

No new tools, no new parameters, no new credentials, no new network destinations, no dependency changes. The other five tools are byte-identical to 0.0.1. No breaking changes.

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

Unchanged from 0.0.1. The plugin makes outbound HTTPS requests only to api.enconvert.com and, to inline Perceive URL's text output, to the signed storage URL that API returns (nyc3.digitaloceanspaces.com); both are declared in manifest.yaml under network.domains. No user input reaches the host or scheme of any request. URLs passed to Perceive URL, Discover URLs and Extract Structured are fetched by EnConvert's servers, never by the Dify host. The two convert tools take a Dify file input, not a URL. No command, code, SQL, shell or filesystem access; no bundled binaries; no telemetry. The user's API key is sent only as the X-API-Key header to api.enconvert.com.

Local validation

$ dify plugin package ./dify-enconvert -o enconvert-0.0.2.difypkg
INFO plugin packaged successfully

Package inspected: manifest version 0.0.2, 24 files, no .env, .venv, __pycache__ or .git. An offline test drives all six tools through their real _invoke against a stubbed HTTP transport and asserts each POSTs to the correct endpoint and that the convert tools upload the file correctly; it passes.

The same .difypkg is attached to the source repository's v0.0.2 release, built from tag v0.0.2 (commit 8fd3d67).

Reviewer notes

The "tested on Community Edition and Cloud" box is left unchecked for the same reason as in #2999: the tools were exercised through the plugin runtime and an offline harness rather than inside a running Dify instance. The change is confined to the text of one tool's summary message.