[Liuziyu77]

Plugin Submission

Plugin information

• Author: valen-team
• Plugin name: valen (Valen)
• Version: 0.1.1
• Source repository: https://github.com/Valen-Team/valen-integrations/tree/e49534a375dbd9572dac7c6ae45ab788f33c7093/dify
• Contact: liuziyu77@sjtu.edu.cn

Submission type

• New plugin
• Version update

What changed

Valen adds four tools for structured judgments over text and an optional image: Yes/No, Choice, Score and Evaluate. Answers include probabilities and declared workflow variables. A workflow can route support tickets, inspect image attributes or prioritize alerts without parsing generated prose. Yes/No exposes an explicit intermediate review branch; failed requests raise tool errors instead of producing a negative answer.

This is the first Marketplace submission. Version 0.1.1 adds Marketplace source/contact metadata, outbound-domain disclosure, localized documentation and an expanded privacy policy to the existing 0.1.0 GitHub distribution. API behavior and tool schemas are unchanged. The public GitHub release includes a starter workflow with separate normal, review and request-failure paths. The example returns data only; it does not perform business actions.

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 Development Guidelines.
• 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

• User-controlled network destinations / URL fetching: the workspace operator configures a Valen-compatible Base URL in provider credentials, including trusted self-hosted HTTP(S) servers. API paths are fixed to /v1/models and /v1/decisions, but hostnames are not restricted to a fixed allowlist. The Dify SDK downloads an optional image's file URL. High risk is selected conservatively for these configurable destinations. Instance administrators must apply their Dify network and file-access policies; this plugin does not claim to prevent SSRF at the instance boundary.
• External content processing: supplied text, questions, selected model and optional image bytes are sent to that configured API. Free-form inputs may include personal or sensitive data if a workflow supplies them. README and privacy policy explain this boundary. The plugin does not read other workspace files or records.
• Credentials: the optional API key is a Dify secret provider field, used only as the configured API's authorization header. It is not attached to image downloads. No embedded credentials, content logging or persistent storage are added by the plugin.
• Constraints and timeouts: one PNG/JPEG/WebP image; input questions, answer distributions and thresholds are validated. API calls have a 120-second per-attempt timeout with two retries for supported transient failures; the overall plugin request limit is 420 seconds. Dify SDK 0.10.2 file downloads use its configurable HTTPX timeout (5 seconds by default).
• No command/code execution, shell, SQL, database writes, SSH/SFTP, browser automation, financial transactions, payment processing or asset/token transfers. Refund wording in the support-ticket example is an intent-classification example. It never issues a refund, contacts a payment processor or changes an account balance.

Local validation

Package built using the official Dify CLI 0.6.12. Validator: langgenius/dify-marketplace-toolkit at 57a21d1304b1108df3e6b90a15a4f5dd9f0915f9.

python3 validator/validate-difypkg.py valen-0.1.1.difypkg \
  --pr-body-file pr-body.md --output-dir validation-report

Result: exit code 0, zero blocking failures, zero environment/check execution failures. Package contents, secrets, binaries, manifest, README, dependencies, Python compilation and sensitive-capability disclosure all passed. Online lookup found no known vulnerabilities in the three directly pinned dependencies. Informational/manual-review findings cover the refund example, runtime-built destinations and disclosed network access.

Dify-specific SDK registration and adapter checks: 2 passed on Python 3.12 with dify-plugin==0.10.2. They cover all four registered tools, declared outputs, credential validation, real SDK transport against a local fixture, unsupported images and errors.

Reviewer notes

• Tested platform: Dify Community Edition 1.18.0, Python 3.12 plugins. The 0.1.0 runtime passed the imported support workflow's yes/no/unsure, separate API-error and uploaded PNG paths, plus Choice/Score/Evaluate. Version 0.1.1 preserves the runtime logic apart from the versioned User-Agent and passes the Dify SDK/adapter checks. A fresh full 0.1.1 platform run was not repeated because the disposable local instance is currently stopped.
• Dify Cloud was not tested. This is disclosed instead of claiming Cloud acceptance. Marketplace install CI should exercise the exact submitted package.
• The existing community distribution is unsigned; it requires an instance that permits unsigned plugins. No signature bypass is performed by the plugin. Marketplace signing and distribution are handled by the official review pipeline.
• Expected validator warnings: refund-related words in the demonstration README are classified as possible payment-processing signals; no payment operation exists. Runtime-built API URLs are intentional and disclosed above. The bundled dependencies are Python packages, not executables or local runtime environments.
• Primary README is English; Simplified Chinese is in readme/README_zh_Hans.md. Maintainer instructions and demonstration workflow files are excluded from the runtime package and distributed separately.

Public package and starter workflow: https://github.com/Valen-Team/valen-integrations/releases/tag/dify-v0.1.1

Submitted package SHA256: 357b79accdf1be3718fcae24cc118e4cdc4a644056c6a22596a1eb6c16b2852d.

[crazywoola]

Pre Check Plugin and PR Risk Label passed for this revision. Inspected the submitted package, documentation and relevant source: this is a non-draft plugin submission with no Web3 functionality identified. This is an eligibility review, not a comprehensive security audit.