Skip to content

Update plugin: jcaiagent7143-ui/linkdigest v0.1.6 - #3618

Merged
crazywoola merged 1 commit into
langgenius:mainfrom
jcaiagent7143-ui:linkdigest-0.1.6
Nov 4, 2026
Merged

crazywoola merged 1 commit into
langgenius:mainfrom
jcaiagent7143-ui:linkdigest-0.1.6

Conversation

@jcaiagent7143-ui

Copy link
Copy Markdown
Contributor

Plugin Submission

Plugin information

Submission type

  • New plugin
  • Version update

What changed

README copy only, plus the version number. No code, no tool parameter, no new dependencies, no new permissions, no new network domains. Between 0.1.5 (the version on the marketplace) and 0.1.6 three packaged files differ: README.md, README.zh_Hans.md and manifest.yaml (version only).

  1. Pricing section. It listed only the card prices ($5 once for 250 credits, $9/month for 500). It now also names the smaller one-time pack (50 credits, payable by Alipay in CNY or by card at $1.50) and states the per-read formula with two worked examples: an image post is 1 credit for up to 6 images, +1 per further 6; a video is 1 credit plus 1 per started minute. These are the service's current published prices.
  2. Platform table. Three rows added for sources the service already reads: Weibo posts, WeChat Official Account articles, and podcast episodes (Xiaoyuzhou and Apple Podcasts).

The localized README carries the same two changes in Chinese.

Unchanged and still true: one tool, digest_url; the plugin runs nothing locally and fetches only https://linkdigest.dev with the user's own key; the user's URL is sent as a JSON field and the service performs the fetch on its side; credential validation hits an endpoint that starts no digest and spends no credit.

Risk level

  • Low risk
  • Medium risk
  • High risk

Unchanged since 0.1.0: the tool accepts a user-provided URL and sends it to an external service. The plugin itself fetches only linkdigest.dev; it does not fetch the user's URL. The service reads public posts only — no login, no cookie — and returns text. This version changes documentation only.

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.

README.md is entirely English (a test in the source repository fails the build on any CJK character in it); localized prose lives in README.zh_Hans.md.

Limitation, documented as the third check requires: as with earlier versions, I have not run this inside a Dify Community Edition or Dify Cloud instance. The code is byte-identical to 0.1.5, which is live on the marketplace; what was checked is in Local validation below.

Security and privacy notes

  • Network destination: linkdigest.dev only (declared in manifest.yaml), over HTTPS. Unchanged.
  • Read-only tool. No command execution, no code execution, no SQL, no filesystem access, no browser automation, no proxying or crawling.
  • The plugin does not fetch arbitrary URLs. The user's URL is sent as a JSON field to the LinkDigest API, which validates it and performs the fetch on its side.
  • Personal data: unchanged from 0.1.5. PRIVACY.md is unchanged.
  • API key is stored by Dify's credential store, sent only as an Authorization: Bearer header, never logged, and not echoed in error messages.

Local validation

$ dify-plugin-darwin-arm64 version          # official CLI from langgenius/dify-plugin-daemon releases
v0.6.10
$ dify-plugin-darwin-arm64 plugin package ./linkdigest -o linkdigest-0.1.6.difypkg
INFO plugin packaged successfully

$ unzip -l linkdigest-0.1.6.difypkg          # same 15 entries as 0.1.5
LICENSE, PRIVACY.md, README.md, README.zh_Hans.md, _assets/icon.png, linkdigest_client.py,
main.py, manifest.yaml, provider/{__init__.py,linkdigest.py,linkdigest.yaml}, requirements.txt,
tools/{__init__.py,digest_url.py,digest_url.yaml}
no __pycache__, no .env, no .git, no virtualenv; key-material regex finds nothing

$ git diff --stat e9a4f1c 9c25318 -- dify/   # in the source repository, 0.1.5 -> 0.1.6
dify/README.md, dify/README.zh_Hans.md, dify/manifest.yaml (version)
(plus dify/examples/social-research-agent.yml restored in the repository; it is not part of the package)

Reviewer notes

Single file added: jcaiagent7143-ui/linkdigest/linkdigest-0.1.6.difypkg. The earlier packages are left in place, as with previous version updates. Source is public in the repository above under dify/, identical to the package contents.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GeFw3jSg2nBc2Ufd496obe

@github-actions github-actions Bot added the risk: medium Medium-risk Marketplace submission label Nov 3, 2026

@crazywoola crazywoola left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pre Check Plugin and PR Risk Label passed for this revision. Inspected the 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.

@crazywoola
crazywoola merged commit a8b07c5 into langgenius:main Nov 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: medium Medium-risk Marketplace submission

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants