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 →
Data as of (UTC)
What it doesAI
基于 Docker 一键部署 DeepSeek Harness 网页版,提供对话、工作区和插件市场。
- Docker 一键部署,浏览器访问完整 Web 界面
- 内置工作区,支持网页内目录浏览和新建文件夹
- 插件市场可搜索并安装 GitHub dsh 插件
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:Tom6814/dsh-webInstall method: GitHub · runtime test inconclusive (L5 unknown)
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.
5 samples (roughly every 14 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-05 · 5 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-01 → 11-05 · 4 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 current | dsh 0.2.2-rc.1 | dsh 0.2.2-alpha.2 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 |
|---|---|---|---|---|---|
| 670748 | ○ | ○ | ○ | ○ | ○ |
| 1888d0 | · | · | · | · | · |
| 07a209 | ○ | ○ | · | · | · |
670748github✓ 5 runtime-verified○ 15 ecosystem plugin2026-11-14
https://github.com/Tom6814/dsh-web
○dsh 0.2.2-rc.3current2026-11-14Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-14 · expires: 2026-11-21
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-07 · expires: 2026-11-14
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-alpha.22026-11-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-alpha.2
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.2.2-alpha.2 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-02Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-02 · expires: 2026-11-09
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-25 · expires: 2026-11-01
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.12026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-28Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-28 · expires: 2026-10-05
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.12026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-alpha.12026-09-22Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.1
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.1.7-alpha.1 · profile: l4-sandbox
Issued: 2026-09-22 · expires: 2026-09-29
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-21Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-21 · expires: 2026-09-28
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
active in loader tree (149 entries)
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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
active in loader tree (149 entries)
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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
active in loader tree (149 entries)
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-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.1.2-alpha.12026-09-02L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: artifact unstated (historical)
ID: dsh-web@670748@dsh0.1.2-alpha.1 · profile: l5-web-smoke
Issued: 2026-09-02 · expires: 2026-12-01
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
active in loader tree (148 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web (version unstated)
ID: dsh-web@670748@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.
1888d0github✓ 1 runtime-verified2026-09-04
github:Tom6814/dsh-web
✓dsh 0.1.2-rc.12026-09-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · github:Tom6814/dsh-web#1888d0
ID: dsh-web@1888d0@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-04 · expires: 2026-12-03
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
active in loader tree (149 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
07a209github○ 2 ecosystem plugin2026-11-16
https://github.com/Tom6814/dsh-web
○dsh 0.2.2-rc.3current2026-11-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web#07a20963a9e6d3adb62c657c94be4e1c58684d91
ID: dsh-web@07a20963a9e6d3adb62c657c94be4e1c58684d91@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-13Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/Tom6814/dsh-web#07a20963a9e6d3adb62c657c94be4e1c58684d91
ID: dsh-web@07a20963a9e6d3adb62c657c94be4e1c58684d91@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-13 · expires: 2026-11-20
View checks & evidence
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-web@07a209…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-web/?ref=badge)``[](https://www.dsh.so/artifact/dsh-web/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-web/?ref=badge-install)`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.
—07a20963a9e6git2026-11-1707a20963a9e6same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningshellExec · shell
plugins/automation/lib/index.js:103const child = execFile( - warningnetIp · network
plugins/github-sync/lib/index.js:51if (!publicOrigin) publicOrigin = 'http://127.0.0.1:' + (process.env.PORT || '3081'); - warningnetIp · network
plugins/mcp-skill/lib/index.js:154if (!publicOrigin) publicOrigin = 'http://127.0.0.1:' + localPort; - warningnetIp · network
start.sh:183proxy_pass http://127.0.0.1:__LISTEN__; - warningnetIp · network
start.sh:186proxy_set_header Origin http://127.0.0.1:__LISTEN__; - warningnetIp · network
start.sh:198proxy_pass http://127.0.0.1:$preview_port$preview_path$is_args$args;
show 6 audit findings
- high/api/mcp-skill/server spawns an arbitrary binary+args and re-spawns it on every boot
plugins/mcp-skill/lib/index.js:196The upsert handler copies `b.command`, `b.args`, `b.env` verbatim into the store and calls applyHot(), which reaches this StdioClientTransport and spawns the process with inherited environment. Nothing validates the command, and no authentication guards the endpoint. The config is persisted to $DSH_HOME/mcp-skill.json with enabled:true and `applyHot(loadStore().servers)` runs at module load, so a single POST yields arbitrary command execution that survives restarts (persistence). The same reject/import paths (parseCursorJson, /import-cursor) feed the same sink.
- highnginx rewrites Host/Origin to loopback, defeating dsh's trust fence and publishing all APIs unauthenticated
start.sh:219dsh deliberately refuses non-loopback Host/Origin; this proxy makes every remote request look loopback, so the host-trust/origin fence no longer protects anything. Combined with the `listen 0.0.0.0:$PORT` server block and the `location ~ ^/preview/port/([0-9]+)` proxy to arbitrary 127.0.0.1 ports (line ~199 `proxy_pass http://127.0.0.1:$preview_port$preview_path$is_args$args;`), any internet client can reach the automation/mcp-skill/github-sync endpoints — i.e. the command-spawning surfaces above — and probe any local port.
- mediumAutomation API runs the headless agent with an attacker-supplied prompt in an arbitrary, auto-created cwd
plugins/automation/lib/index.js:103`args.push(prompt)` comes from the request body, and `cwd = taskWorkspace(task)` uses `task.cwd` set via /api/automation/create|update, calling `mkdirSync(task.cwd.trim(), { recursive: true })` on an arbitrary path. Each POST /api/automation/run therefore creates directories anywhere the process can write and launches a full tool-enabled agent on attacker-chosen instructions in that directory; the same sink backs /automation/optimize. execFile is not shell-string interpolation, so there is no classic argument injection, but the effect is agent-level command execution from an unauthenticated HT
- mediumGitHub token and OAuth client secret persisted in plaintext and partly disclosed via /config
plugins/github-sync/lib/index.js:43The OAuth access token (scope `repo user:email`, i.e. full private-repo access) and the OAuth app client secret are written to $DSH_HOME/github-sync.json with default permissions, readable by any process/user that can read the data volume, and /api/github-sync/config then reports the bound account + email to any web client. There is no encryption, no file mode hardening, and no logout revocation of the remote token.
- lowSession lookup by title scans and decompresses every stored session
plugins/github-sync/lib/index.jsGET /api/github-sync/session?title= iterates every directory under $DSH_HOME/sessions and decompresses each session.jsonl.zstd to compare titles/first user message, returning the resolved sessionId and cwd. Any web client can therefore enumerate all sessions and their workspace paths (cross-session metadata disclosure) and force unbounded CPU/IO work by repeated calls; the match is also loose (substring both directions) so the wrong session can be returned.
- lowGlobal uncaughtException/unhandledRejection handlers swallow all process errors
plugins/mcp-skill/lib/index.jsThe handler only logs and returns, so any uncaught error anywhere in the host — including inside the spawned MCP transports and the HTTP handlers — leaves the process running in an unknown state instead of failing fast; errors from the command-executing paths above could be silently masked. It also masks real crashes from operators.
mcp-skill and automation expose unauthenticated HTTP endpoints that spawn arbitrary processes, and start.sh publishes the harness with dsh's host/origin fence rewritten to loopback.
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-08-17 · activity: Inactive
• Repo created: 2026-08-13
• Stars: ★ 3 · Forks: 1
• Health: Inactive — no commit in 90+ days
Source
GitHub: github.com/Tom6814/dsh-web
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-web?
dsh-web 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.
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-web?
Run dsh plugin --profile web add github:Tom6814/dsh-web 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.
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-17 (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.
