Skip to content

docs(plugins): add safe community listing guidance / 添加安全的社区插件收录指南 - #7166

Open
kashifmahi wants to merge 2 commits into
esengine:main-v2from
kashifmahi:docs/community-plugins
Open

docs(plugins): add safe community listing guidance / 添加安全的社区插件收录指南#7166
kashifmahi wants to merge 2 commits into
esengine:main-v2from
kashifmahi:docs/community-plugins

Conversation

@kashifmahi

@kashifmahi kashifmahi commented Aug 1, 2026

Copy link
Copy Markdown

Summary

  • Add English and Chinese Community Plugins pages with a complete, pinned [[plugins]] adoption example.
  • Link the pages from both README navigation bars.
  • Position the page as a Reasonix-specific complement to the official MCP Registry.
  • Document the MCP trust boundary and require reachable public source plus a versioned release before listing a community server.
  • Keep the list empty until an entry satisfies those provenance requirements.

Issue

Closes #7165

Security

  • Installing or declaring an MCP server is explicitly documented as a trust decision.
  • readOnlyHint and destructiveHint are identified as workflow metadata, not containment against malicious code.
  • The example pins the package version and uses npx -y so the first-run prompt cannot block the stdio handshake.

Verification

  • git diff --check
  • English and Chinese Guide anchors verified
  • README and local documentation targets verified
  • Synthetic merge tree with the latest main-v2 verified

Cache impact

  • Cache-impact: none
  • Cache-guard: N/A; documentation only
  • System-prompt-review: N/A; no provider-visible prompt, memory prefix, tool schema, or request serialization changes

@github-actions github-actions Bot added the v2 Go rewrite (1.x) — main-v2 branch, active development label Aug 1, 2026
Problem:
The initial community page linked an inaccessible source repository, used an interactive and unpinned npx command, and omitted the Chinese documentation path.

Root cause:
The listing requirements did not make public provenance, reproducible install commands, or bilingual navigation explicit.

Fix:
Remove the unverifiable entry, document the official Registry relationship and MCP trust boundary, use a pinned non-interactive npx example, and add the matching Chinese page and README link.

Verification:
- git diff --check
- local documentation targets and Guide anchors verified
- latest main-v2 merge tree checked
@SivanCola SivanCola changed the title docs(plugins): add community plugins page and adoption example docs(plugins): add safe community listing guidance / 添加安全的社区插件收录指南 Aug 2, 2026
@SivanCola

Copy link
Copy Markdown
Collaborator

I pushed c71a623 to address the documentation, startup, and provenance findings.

What changed:

  • added the matching Chinese page and README navigation entry
  • documented the official MCP Registry relationship and the actual MCP trust boundary
  • changed the example to a pinned, non-interactive npx -y launch
  • required reachable public source and a versioned release for every community listing
  • removed reasonix-plugin-git-context from the list because its declared public source repository currently returns 404

The npm 0.1.0 artifact is still published, but it should not be promoted from the official README until users can inspect the corresponding source. Once the repository is publicly reachable, the plugin can be re-added with its complete pinned [[plugins]] configuration.

Verified:

  • git diff --check
  • English and Chinese Guide anchors and local documentation targets
  • synthetic merge tree with the latest main-v2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v2 Go rewrite (1.x) — main-v2 branch, active development

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Docs: add a "Community plugins" page

2 participants