DeepSeek Harness 插件

dshplugins

Check the dsh plugins you already installed against a registry of verified packages: which ship a broken package, which are pinned to a dsh version that no longer exists, and which run code on your(英文原文)

跳到安装方式

来源信息

GitHub 仓库
stimQQ/dshplugins
最近更新
2026年8月16日
分类
插件市场与管理
GitHub stars
0
载体类型
plugin
包路径
packages/dsh-plugin-check
目录证据
上游声明已找到 dsh.bundle
证据路径
packages/dsh-plugin-check/package.json#dsh.bundle
核对版本
0.1.0-rc.8
上游核对日期
2026-08-20

该证据由上游目录提供。本站没有安装、运行或安全审核这个插件。

安装

默认先复制一段 Prompt,让 Agent 读 GitHub 仓库和源码;需要自己装时再切到命令。

复制这段 Prompt,发给 DSH、Codex 或其他 Agent,让它先读 GitHub 仓库和源码。

请先不要安装或执行任何命令。阅读这个插件的 GitHub 仓库、README 和关键源码,然后用清楚、直接的方式回答以下问题,帮助我判断它是否适合我的需求:

1. 这个插件是什么,解决什么问题;
2. 适合哪些用户和典型使用场景;
3. 安装后如何使用,并给出一个最小使用示例;
4. 有哪些已知限制,以及隐私、安全、兼容性或维护风险;
5. 给出“推荐 / 有条件推荐 / 不推荐”的明确建议和理由。

请区分仓库明确说明、根据源码推断和未知信息。证据不足时请明确说明,不要猜测或照抄 README。

GitHub:https://github.com/stimQQ/dshplugins/tree/HEAD/packages/dsh-plugin-check
插件名:dshplugins
作者:stimQQ

检查来源文件

安装前先看这个插件目录里的 README 和其他文件。

文件资源管理器2 个文件
README.md来源说明 · 只读预览

dsh-plugin-check

Check the DeepSeek Harness plugins you already installed, and draft the issue that fixes each problem.

Every plugin marketplace answers what could I install. None of them answers is what I installed still working — which is the question that decays: dsh went 0.0.1-rc.10.1.0-rc.6 in its first five days, so a plugin that installed cleanly last week can be pinned to a range that no longer resolves.

Install

dsh plugin --profile web add dsh-plugin-check

Use

Ask the agent to check your plugins. It calls the plugin_check tool, which reads the profiles under $DSH_HOME, asks dshplugins.co what it knows about each installed package, and reports the difference.

Checked 6 installed plugin(s): 4 with problems, 0 not in the registry.

[web] @nanmicoder/dsh-agent-teams
  error: depends on @deepseek-ai/dsh-llm@^0.0.1-rc.1, but npm now ships 0.1.0-rc.6

[web] @a834063245/hologram-dsh
  error: rows-resolvable: 1 row(s) name something an install cannot resolve

Pass draftReports: true and it also writes an issue body per problem plugin, naming the exact edit that fixes it, ready to file against that plugin's repository.

What it reports

FindingMeaning
patch-shippedThe declared cordis.patch.yml never shipped — the plugin installs and the layer is not there
rows-resolvableA patch row names something an install cannot resolve, usually the package's pre-publish name
client-half-shippedA declared browser half is missing — it boots fine and the UI never appears
prebuiltSource only, so installing runs its build script on your machine
stale rangeIts dsh dependency range excludes the version npm ships today

It is read-only

It never installs, upgrades, or removes anything. Most of what it finds can only be fixed by the plugin's author, which is why it drafts the report rather than pretending to repair.

It reads packaging, not code: a plugin with nothing reported can still be malicious or useless. Treat it as a dead-on-arrival filter, not a safety endorsement — a plugin runs inside the dsh process with everything dsh can reach.

Configuration

- id: plugin-check
  name: dsh-plugin-check
  config:
    registry: https://dshplugins.co   # any host serving the same /api/v1 shape
    timeoutMs: 8000

Data comes from the free dshplugins.co API (CC BY 4.0), which downloads every published tarball daily and checks it against what its manifest claims.

MIT