Skip to content

bump(contrastapi): 0.9.0 -> 0.10.0 (well_known, epss_risers) - #3867

Open
UPinar wants to merge 1 commit into
langgenius:mainfrom
UPinar:contrastapi-0.10.0
Open

UPinar wants to merge 1 commit into
langgenius:mainfrom
UPinar:contrastapi-0.10.0

Conversation

@UPinar

@UPinar UPinar commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Plugin Submission

Plugin information

Submission type

  • New plugin
  • Version update

What changed

The tools are generated from the ContrastAPI server's OpenAPI description. Version 0.10.0 follows the server's current description:

  • Two new tools: well_known reads the robots.txt and the security.txt of a web site, and epss_risers lists the CVEs whose EPSS score rose most over 7 or 30 days.
  • cve_search takes kev_added_after, and its sort takes kev_date_added.
  • Each tool parameter carries the description that the server gives it.

No tool was removed or renamed, so workflows built on 0.9.0 keep working.

Single versioned .difypkg change only.

Risk level

  • Low risk
  • Medium risk
  • High risk

The password_check tool, unchanged since 0.9.0, takes a password as input, which is authentication data. The plugin computes the SHA-1 of the password itself and sends only that hash to ContrastAPI; the password text is never sent. ContrastAPI sends Have I Been Pwned only the first 5 hex digits of the hash (k-anonymity range query). SHA-1 is used because the HIBP range API requires it, not for security. PRIVACY.md says this and warns that the typed text still passes through the AI model and Dify's own logs.

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

  • password_check: see Risk level above. The plugin sends a SHA-1 hash, never the password.
  • well_known sends the domain name to the ContrastAPI server, which fetches that site's robots.txt and, when robots.txt allows it, its security.txt. The plugin itself fetches no URL of the user's choice; it calls only the ContrastAPI host.
  • Domain, host name, IP address and e-mail tools send the value the user gives to the ContrastAPI server, which looks it up.
  • The optional API key is a secret credential field and is sent only to the ContrastAPI host.

Local validation

  • Package built from the committed source with dify-plugin plugin package (CLI): plugin packaged successfully, 89 files, no test, script or cache files.
  • The generator tests, the plugin tests and the generator's up-to-date check pass on the committed source.

Reviewer notes

  • This version was not yet installed on a Dify instance. 0.9.0, built by the same generator, was installed and run on a self-hosted Dify Community Edition. Dify Cloud was not tested.

@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