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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.Install verification details →
Data as of (UTC)
What it doesAI
A monorepo of plugins for DeepSeek Harness: LAN/remote access gateway and a vision tool for agents.
- LAN/remote access gateway with token gate and loopback exempt
- crypto.randomUUID polyfill and settings persistence exemptions
- Vision tool for agents to describe local images
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:TZHR-invest/dsh-plugins#v0.1.0Install method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.2-rc.3
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
10 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-15 · 10 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
10-02 → 11-15 · 9 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
Only 0 points (< 3): no chart yet
no data yet
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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v0.1.0 | ○ | ○ | ○ | ○ | ○ |
v0.1.0github○ 15 ecosystem plugin2026-11-18
https://github.com/TZHR-invest/dsh-plugins
○dsh 0.2.2-rc.32026-11-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-18 · expires: 2026-11-25
View checks & evidence
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.2-rc.12026-11-06Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
View checks & evidence
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-rc.52026-11-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
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-rc.32026-10-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
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-rc.22026-10-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
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.42026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
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-12Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
View checks & evidence
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.0-rc.22026-10-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
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.1.7-rc.22026-09-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
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.1.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
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.1.6-alpha.12026-09-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
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.1.5-rc.22026-09-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
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.1.3-alpha.22026-09-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
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.1.3-alpha.12026-09-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
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.
○prehistory2026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/TZHR-invest/dsh-plugins#v0.1.0
ID: dsh-plugins-76@v0.1.0@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
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.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
Author badges
Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-plugins-76/?ref=badge)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
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.
Static low; dynamic high (authoritative when present) → overall high.
—v0.1.0git2026-11-19v0.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (11)
- warningnetIp · network
packages/dsh-lan-access/reapply-lan-patches.sh:246curl -s --noproxy '*' -o /dev/null -w '127.0.0.1:3080 页面(回环豁免,应 200)-> %{http_code}\n' http://127.0.0.1:3080/ - warningnetIp · network
packages/dsh-lan-access/reapply-lan-patches.sh:251curl -s --noproxy '*' -o /dev/null -w 'LAN Host settings.describe(带令牌,应非 403)-> %{http_code}\n' -H "Host: $IP:3080" -H "X-DSH-Token: $TOKEN" - warningnetIp · network
packages/dsh-lan-access/reapply-lan-patches.sh:254curl -s --noproxy '*' -o /dev/null -w '插件 bundle(应 200)-> %{http_code}\n' http://127.0.0.1:3080/plugins/dsh-lan-gateway/client.js - warningcurlDownload · network
packages/dsh-lan-access/reapply-lan-patches.sh:246curl -s --noproxy '*' -o /dev/null -w '127.0.0.1:3080 页面(回环豁免,应 200)-> %{http_code}\n' http://127.0.0.1:3080/ - warningcurlDownload · network
packages/dsh-lan-access/reapply-lan-patches.sh:248curl -s --noproxy '*' -o /dev/null -w "$IP:3080 无令牌(应 401 登录页)-> %{http_code}\n" "http://$IP:3080/" - warningcurlDownload · network
packages/dsh-lan-access/reapply-lan-patches.sh:250curl -s --noproxy '*' -o /dev/null -w "$IP:3080 带令牌(应 200)-> %{http_code}\n" -H "X-DSH-Token: $TOKEN" "http://$IP:3080/" - warningnetIp · network
packages/dsh-mobile-ui/install.sh:232curl -s -o /dev/null -w " 127.0.0.1:3080 页面 -> %{http_code}\n" http://127.0.0.1:3080/ || echo " [警告] 页面未就绪,请稍后手动刷新" - warningnetIp · network
packages/dsh-mobile-ui/install.sh:233curl -s -o /dev/null -w " $PLUGIN bundle -> %{http_code}\n" "http://127.0.0.1:3080/plugins/$PLUGIN/client.js" - warningcurlDownload · network
packages/dsh-mobile-ui/install.sh:232curl -s -o /dev/null -w " 127.0.0.1:3080 页面 -> %{http_code}\n" http://127.0.0.1:3080/ || echo " [警告] 页面未就绪,请稍后手动刷新" - warningcurlDownload · network
packages/dsh-mobile-ui/install.sh:233curl -s -o /dev/null -w " $PLUGIN bundle -> %{http_code}\n" "http://127.0.0.1:3080/plugins/$PLUGIN/client.js" - warningchildProcess · code-exec
packages/dsh-vision/index.js:103const proc = spawn("curl", cmd, {
show 5 audit findings
- highLAN token gate skipped when attacker spoofs a loopback Host header
packages/dsh-lan-access/token-gate.js:39The gate is wired in as `if (!lanGateIsLoopback(req) && lanGateRequest(req, res)) return;`, so any LAN client that sends `Host: localhost:3080` is classified as loopback and the entire token check is skipped. Combined with the dex patch that restores privileged RPC handling for non-loopback origins (dsh-client-connection patch) and the 0.0.0.0 bind, an unauthenticated network neighbour reaches the DSH web UI/API without any token and without user action.
- mediumToken gate fails open when the token file is missing or empty
packages/dsh-lan-access/token-gate.js:56lanGateReadToken() returns "" on any read error; the gate then treats every request as authorized. If token generation fails (the reapply script prints "无法生成随机令牌(需要 node 或 openssl)") or the file is deleted/unreadable, the LAN-exposed webserver keeps running with the privileged-fence patch applied and no authentication at all.
- mediumInstaller sed-patches installed host library to relax the privileged-RPC fence
packages/dsh-lan-access/reapply-lan-patches.sh:176The script rewrites @deepseek-ai/dsh-client-connection/lib/index.js inside node_modules so that privileged RPC methods are accepted from origins in trustedHosts rather than being rejected. The only compensating control is the LAN token gate, which is bypassable (see finding 1) and fails open (finding 2); the change is silently re-applied after every dsh upgrade, so it survives remediation and is not visible in the plugin code itself.
- mediumVision plugin passes API key on the curl command line, exposing it to local process listings
packages/dsh-vision/index.js:98The bearer credential is placed in argv, so any local user able to read /proc/<pid>/cmdline or run ps can recover the vision API key for the whole 150 s request window (and via shell history/logging of spawned argv). The key is also included on every cross_check call, multiplying exposure.
- lowToken accepted via URL query string and stored in a cookie without Secure over cleartext HTTP
packages/dsh-lan-access/token-gate.js:62The LAN access token is the sole credential for the whole harness. Accepting it as ?token=/#?dsh_token= leaks it into browser history, server access logs, proxy logs and Referer headers, and the session cookie (dsh_lan_token, plaintext token value, no Secure flag, because the design uses cleartext HTTP) is replayable by anyone able to sniff the LAN.
LAN token gate bypassable via spoofed Host header and fails open without a token file; installers also relax a host privilege check and leak API keys via curl argv.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.
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-10-13 · activity: Stable
• Repo created: 2026-08-14
• Stars: ★ 3 · Forks: 1
• Health: Stable — committed within 90 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
Frequently asked questions
What is dsh-plugins?
dsh-plugins is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install dsh-plugins?
Run dsh plugin --profile web add github:TZHR-invest/dsh-plugins#v0.1.0 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-11-19 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.
