Skip to content

feat: add Context.dev plugin - #2985

Open
aadithyanr wants to merge 1 commit into
langgenius:mainfrom
aadithyanr:feat/context-dev-plugin
Open

feat: add Context.dev plugin#2985
aadithyanr wants to merge 1 commit into
langgenius:mainfrom
aadithyanr:feat/context-dev-plugin

Conversation

@aadithyanr

Copy link
Copy Markdown

Plugin Submission

Plugin information

Submission type

  • New plugin
  • Version update

What changed

Adds six Context.dev tools for live web search, URL-to-Markdown scraping, bounded website crawling, sitemap page discovery, JSON Schema extraction, and brand profiles. The plugin calls the fixed production API at https://api.context.dev/v1 and does not include the unreleased Answers endpoint.

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

This plugin performs arbitrary public URL fetching and bounded crawling, so it is classified as high risk. It connects only to https://api.context.dev/v1; the API base cannot be overridden. Crawl and extraction page counts are bounded, every request has a fixed timeout, and API keys are sent only in the Authorization header and redacted from surfaced API errors. The plugin executes no user code, shell commands, SQL, filesystem operations, browser automation, or webhook forwarding.

Search queries, URLs, domains, schemas, instructions, and request options are sent to Context.dev as documented in PRIVACY.md.

Local validation

  • uvx ruff check . — passed
  • uvx ruff format --check . — passed
  • .venv/bin/python -m pytest -q -m 'not live' — 10 passed
  • .venv/bin/python -m pytest -q -m live — credential, search, scrape, sitemap, brand, crawl, and extraction paths passed against https://api.context.dev/v1
  • dify plugin package — passed
  • Unpacked package loaded with official dify-plugin==0.9.1; all six tool mappings resolved
  • unzip -t — passed
  • Archive inspection confirmed no secrets, environments, caches, tests, workflows, binaries, or unreleased Answers endpoint

Reviewer notes

A Dify Community Edition or Dify Cloud workspace was not available in this environment. The package was instead loaded and resolved through the official Dify Python SDK, and every public tool path was smoke-tested against the production Context.dev API. No executable or bundled binary is included.

@github-actions github-actions Bot added the risk: high High-risk Marketplace submission label Aug 29, 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