Skip to content

Add plugin onlinecompiler/onlinecompiler v0.0.1 - #3870

Open
ashwin31 wants to merge 1 commit into
langgenius:mainfrom
ashwin31:add-onlinecompiler
Open

ashwin31 wants to merge 1 commit into
langgenius:mainfrom
ashwin31:add-onlinecompiler

Conversation

@ashwin31

Copy link
Copy Markdown

Plugin Submission

Plugin information

Submission type

  • New plugin
  • Version update

What changed

A tool plugin for OnlineCompiler.io, a code execution API. Three tools for workflows and agents:

  • Run Code: runs a program in one of 46 languages with optional stdin and returns stdout, stderr, exit code, time and memory.
  • Run Tests: runs a program against test cases (input and expected output) and returns a verdict, a score and a result for each test.
  • List Compilers: lists the compiler ids the other two tools accept.

The provider takes an OnlineCompiler.io API key (free plan available) and checks it when saved.

Risk level

  • Low risk
  • Medium risk
  • High risk

The plugin executes code, so it is High risk under the classification. The code is not run on the Dify host: the plugin sends it over HTTPS to the OnlineCompiler.io API, which runs it in a fresh gVisor sandbox with no network access.

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

  • Code execution: yes, but remote. Code, stdin and test cases are sent to https://api.onlinecompiler.io and run there in a fresh gVisor container per run: no network, an unprivileged user, a read-only image, a 30-second limit and capped memory. Nothing is executed on the Dify host or in the plugin process.
  • Network: the plugin only calls the fixed address https://api.onlinecompiler.io (no user-controlled URLs, redirects not followed). Every request has connect and read timeouts.
  • Credentials: the API key is a secret-input provider credential, sent only as the Authorization header to api.onlinecompiler.io; it is never put in tool output, error messages or logs.
  • Input limits: the plugin refuses a time limit outside 0 to 30 seconds (the sandbox's limit) before sending; input sizes and the number of tests are enforced by the API, whose error is passed on cut to 500 characters.
  • Data: PRIVACY.md lists what is sent and kept (OnlineCompiler.io keeps run history for the account, as in its privacy policy).

Local validation

pytest -q                                          # 135 passed, 8 skipped (live tests need a key)
ONLINECOMPILER_API_KEY=... pytest -q tests/test_live.py   # 8 passed against the live API
dify-plugin plugin package ./dify-plugin-onlinecompiler    # v0.6.15: plugin packaged successfully

Reviewer notes

Tested on Dify Cloud on 21 Nov 2026 through remote debugging (plugin SDK 0.11.0): the API key check passed when the credential was saved; in a workflow, Run Code returned "Hello, Ada!" (exit code 0), Run Tests returned 2 of 2 accepted with score 100, and List Compilers returned the compiler list; in an Agent app (gpt-5), the agent called run_code and answered 2**100 correctly. Not tested on a self-hosted Community Edition: the plugin only makes outbound HTTPS calls to api.onlinecompiler.io and uses no Cloud-only features.

@github-actions github-actions Bot added the risk: high High-risk Marketplace submission label Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: high High-risk Marketplace submission

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant