DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

Plugin Check — DSH Plugin for DeepSeek Harness
← Plugins

dsh-plugin-check

Plugin Check

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 machine at install time. Drafts the issue that fixes each

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add dsh-plugin-check@0.1.0
READMECompatibilityVersions

Compatibility and provenance

Plugin Check is published as dsh-plugin-check and currently resolves to version 0.1.0. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
any
Release source
npm
Registry updated
9/20/2026

Versions

0.1.0stable
8/16/2026

Related plugins

Loading related plugins…

Latest
0.1.0
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
22.6 kB
Files
4
Surface
any
License
MIT
Source
npm
GitHub
★ 0
Weekly downloads
44
Last push
8/16/2026
View source ↗Project homepage ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue
DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in

Related plugins

More verified plugins in security-access.

Doctor@linxin666/dsh-doctorTransactional rescue mode for DSH profiles with a supervised launcher, isolated recovery capsule, deterministic repairs, health monitoring, and a local Web recovery consolePocketdsh-pocketPut DeepSeek Harness in your pocket: one package, one settings page, and scan a QR code on your phone to access DSH on your computer in sync (LAN + public network, real-time screen mirroring).DSCODE@toddzheng024/dscode-bundleA complete DeepSeek coding agent with persistent shell, Ultra collaboration and automatic permission review.Auto Reviewdsh-auto-reviewSecond-model AI auto-review for DeepSeek Harness approval requests: a read-only reviewer subagent decides allow/deny on the approval answerer chain, with fail-closed fallback and full session-log audit.

README

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.1 → 0.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