@nmhwsygxb/dsh-tools

DeepSeek Harness 工具包：自选组件一键安装（远程执行/执行前自动审核/GitHub/联网研究/本地git发布/沙箱逃生/Bug知识库/Blender/上下文压缩/自愈启动器）。组件独立、无个人信息、凭据安装时输入。

Ecosystem pluginAutomationDeveloperProductivityKnowledgeGitHub integrationWeb searchTerminal / Shell

Verification

L5 · Ecosystem plugin

Ecosystem plugin

Risk

Critical

Health

Active

Trust

Silver

Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →

What it doesAI

One-click installer for optional DeepSeek Harness components: remote execution, GitHub, web research, git publishing, bug KB, Blender, compression.

Pick components and install them in one click; credentials entered at install
Remote execution with pre-run auto review plus a self-healing launcher
Adds GitHub, web research, git publishing, bug KB, Blender, compression

automationAIgithubAIweb-searchAIterminalAI

Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.

Installation

dsh plugin --profile web add github:nmhwsygxb/dsh-tools#v1.0.0

verified v1.0.0

Install method: GitHub · runtime test inconclusive (L5 unknown)

Verification & Compatibility○ Ecosystem plugin

Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.

External credentials (plugin-level): none detected

Declared DSH compatibilityfrom package.json · peerDependencies

package manifest not collected

package manifest not collected — the declared range is unknown.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)

○ Ecosystem plugin

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.2 current	dsh 0.2.1-alpha.2
v1.0.0	○	○

Install compatibility (by plugin version, dsh versions within)

Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed

v1.0.0github○ 2 ecosystem plugin2026-10-18

https://github.com/nmhwsygxb/dsh-tools

○dsh 0.2.1-rc.2current2026-10-18Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: github · https://github.com/nmhwsygxb/dsh-tools#v1.0.0

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: dsh-tools-5@v1.0.0@dsh0.2.1-rc.2 · profile: l3-fullscan

Issued: 2026-10-18 · expires: 2026-10-25

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-18

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-18

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec github:nmhwsygxb/dsh-tools#v1.0.0 · channel GitHub source · outcome ran · exit 0

check took: 1.7s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec github:nmhwsygxb/dsh-tools#v1.0.0 · channel GitHub source · outcome ran · exit 0

check took: 1.7s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec github:nmhwsygxb/dsh-tools#v1.0.0 · channel GitHub source · outcome ran · exit 0

check took: 1.7s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-18

spec github:nmhwsygxb/dsh-tools#v1.0.0 · install mode reused L4 scratch

check took: 18ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-18

ready line dsh web: http://127.0.0.1:49816/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-18

path / · HTTP 200 · took 18ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-18

verdict not-found · entries 149

phases: active 121 · null 28

not present in web-profile loader inventory

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

○dsh 0.2.1-alpha.22026-10-14Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.2
• Plugin artifact: github · https://github.com/nmhwsygxb/dsh-tools#v1.0.0

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: dsh-tools-5@v1.0.0@dsh0.2.1-alpha.2 · profile: l4-sandbox

Issued: 2026-10-14 · expires: 2026-10-21

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-18

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-18

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec github:nmhwsygxb/dsh-tools#v1.0.0 · channel GitHub source · outcome ran · exit 0

check took: 9.1s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec github:nmhwsygxb/dsh-tools#v1.0.0 · channel GitHub source · outcome ran · exit 0

check took: 9.1s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec github:nmhwsygxb/dsh-tools#v1.0.0 · channel GitHub source · outcome ran · exit 0

check took: 9.1s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec github:nmhwsygxb/dsh-tools#v1.0.0 · install mode reused L4 scratch

check took: 633ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-14

ready line dsh web: http://127.0.0.1:55843/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-14

path / · HTTP 200 · took 633ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-14

verdict not-found · entries 149

phases: active 121 · null 28

not present in web-profile loader inventory

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

Author badges

Embed the official badges in your README to showcase security & install-test status:

Security Report

Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.

dsh-tools-5Automated review · daily

Static low, dynamic high — stricter wins → overall high.

static low→dynamic high→overall high

0 critical·0 high

highoverall · high

1static scan · vet primaryvet AST static analysis (npm artifact or git source)

Version binding

plugin version—

scanned versionv1.0.0git2026-10-21

current versionv1.0.0same version

vet verdictclean · git

Vet is an AST static scan (npm artifact or git source).

show static findings (7)

warningshellExec · shelltools/01-remote-exec/remote-agent-server.js:93
const out = execSync(command, { timeout: 60000, encoding: 'utf8', maxBuffer: 10 * 1024 * 1024, windowsHide: true })
warningnetIp · networktools/01-remote-exec/remote-agent-server.js:200
console.log(`Remote Agent running on http://0.0.0.0:${PORT}`)
warningcurlDownload · networktools/03-github/github-manager.js:186
Invoke-WebRequest -Uri $env:GH_URL -OutFile $dest -UseBasicParsing -MaximumRedirection 10
warningcurlDownload · networktools/04-web-research/web-research.js:177
Invoke-WebRequest -Uri $env:WR_URL -OutFile $dest -UseBasicParsing -MaximumRedirection 10 -Headers @{ 'User-Agent' = $env:WR_UA }
warningeval · code-exectools/08-blender/blender.js:993
result = eval(compile(expr, '<dsh-blender-result>', 'eval'), ns)
warningshellExec · shelltools/08-blender/blender.js:985
exec(compiled, ns)
warningshellExec · shelltools/08-blender/blender.js:1859
'把任务拆成多次调用，或把长代码放进 .py 文件再用 exec(open(...).read())。');

2dynamic auditmodel reads redacted source context · never executes plugin code

highest gradehigh

merged intooverall high

audited at2026-10-19

findings0 critical·1 high1 medium / 2 low hidden

show 4 audit findings

highStandalone HTTP server executes arbitrary OS commands gated only by a static token over plaintext HTTPtools/01-remote-exec/remote-agent-server.js:112
When the operator runs this script it opens a server on 0.0.0.0 (`server.listen(PORT, '0.0.0.0', ...)`) and GET/POST /exec runs any OS command passed in `command`. The only control is a shared static token compared with `===`, accepted from the query string (`?token=`) or an X-Token header, over unencrypted HTTP, with `Access-Control-Allow-Origin: *`. Token leakage (plaintext transport, URLs in logs/history/proxies, wide CORS) turns this into unauthenticated remote code execution. /exec also accepts GET so a browser can be induced to call it.
mediumBlender“restricted” mode omits `os` and relies on a bypassable regex guardtools/08-blender/blender.js:56
blender_run_python execs model-supplied Python in the host Blender process. The advertised restrictedMode only blocks a fixed module list that omits `os`, and the `guard` is a set of regexes that trivial obfuscation (string concat + getattr) defeats. Prompt-injected content can therefore still call os.system / read arbitrary files, so the hardening does not meaningfully contain it (the code itself admits 'not a sandbox').
lowUnauthenticated /info and /ping leak host, IPs and cwd behind wildcard CORStools/01-remote-exec/remote-agent-server.js
/info and /ping have no auth and responses carry `Access-Control-Allow-Origin: *`, so any web page the user visits can read the agent host's hostname, OS, Node version, LAN IPs and working directory, aiding targeted follow-up (e.g. knowing tokenConfigured/allowDir and reaching the LAN address).
lowwr_fetch/wr_download fetch arbitrary http(s) URLs with no host allowlist (SSRF)tools/04-web-research/web-research.js
The only check is the http(s) scheme; the tool will request URLs pointing at loopback, RFC1918 hosts or cloud metadata (e.g. 169.254.169.254). If the model is steered by prompt-injected page/metadata content it can be used to probe or exfiltrate internal services reachable from the host.

Remote-agent HTTP server exposes networked arbitrary command execution behind only a static token; Blender and web-research guardrails are weaker than advertised.

Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.

Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.

Activity

Last commit 2026-09-22 · activity: Active

• Repo created: 2026-09-13

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/nmhwsygxb/dsh-tools

Plugin notes

What is @nmhwsygxb/dsh-tools?

@nmhwsygxb/dsh-tools is an ecosystem plugin maintained by @nmhwsygxb: it installs via dsh plugin add but declares no dsh.bundle and mounts nothing — installing it adds no plugin capability; use the source repository directly. It is cataloged on dsh.so as a Automation entry, with a public source repository and automated static security scan.

How do I install @nmhwsygxb/dsh-tools?

This is an ecosystem plugin: it installs via dsh plugin add but declares no dsh.bundle and mounts nothing — installing one adds no plugin capability; use the source repository directly. Its level reads L5 · Ecosystem plugin; the security scan still runs.

How does the security scan relate to a manual audit?

Both layers are automated, not a manual audit: the static scan is heuristic analysis of the repository source (it can produce false positives and miss context), and the dynamic security audit has a model read the harvested source context with secret files stripped and content redacted inline — plugin code is never executed. The dynamic audit only covers plugins static-flagged at warn or above, and its conclusion can only raise the combined verdict, never exempt it. Neither layer is a manual security audit or an endorsement; before using a plugin, review the repository and installed permissions, and combine both with the verification level (L4/L5) and health signals.

"DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI. It uses an architecture where everything is a plugin, and is powered by Cordis."
— DeepSeek Harness README

Sources: GitHub repository · DeepSeek Harness README · security scan data · Maintained by dsh.so · Last updated 2026-10-13

@nmhwsygxb/dsh-tools

What it doesAI

Installation

Verification & Compatibility○ Ecosystem plugin

Author badges

Security Report

Activity

Source

Author README