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
A collection of DeepSeek Harness plugins, featuring dsh-todo-guard which auto-reminds the model when it forgets to update its task checklist.
- Collection of individually installable DSH plugins, one folder per plugin
- dsh-todo-guard watches for stale task checklists
- Auto-reminder fires when the model forgets to write back its list
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:wxlei2004/dsh-pluginsInstall method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.2-rc.1
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.
6 samples (roughly every 7 days), 1 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
10-01 → 11-13 · 6 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-09 → 11-13 · 5 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.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| 8f9ef6 | · | · | · | · | · |
| 19f6a8 | ○ | ○ | ○ | ○ | ○ |
8f9ef6local2026-09-28
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
19f6a8github○ 10 ecosystem plugin2026-11-04
https://github.com/wxlei2004/dsh-plugins
○dsh 0.2.2-rc.12026-11-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/wxlei2004/dsh-plugins (version unstated)
ID: dsh-plugins-124@19f6a8@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
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-10-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/wxlei2004/dsh-plugins (version unstated)
ID: dsh-plugins-124@19f6a8@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
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-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/wxlei2004/dsh-plugins (version unstated)
ID: dsh-plugins-124@19f6a8@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/wxlei2004/dsh-plugins (version unstated)
ID: dsh-plugins-124@19f6a8@dsh0.2.1-rc.2 · 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.42026-10-15Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/wxlei2004/dsh-plugins (version unstated)
ID: dsh-plugins-124@19f6a8@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
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-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/wxlei2004/dsh-plugins (version unstated)
ID: dsh-plugins-124@19f6a8@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-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.2.0-rc.22026-10-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/wxlei2004/dsh-plugins (version unstated)
ID: dsh-plugins-124@19f6a8@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.2.0-rc.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/wxlei2004/dsh-plugins (version unstated)
ID: dsh-plugins-124@19f6a8@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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-28Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/wxlei2004/dsh-plugins (version unstated)
ID: dsh-plugins-124@19f6a8@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-28 · expires: 2026-10-05
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-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/wxlei2004/dsh-plugins (version unstated)
ID: dsh-plugins-124@19f6a8@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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.
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-124/?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 medium (authoritative when present) → overall medium.
—763f8870bc65git2026-11-13763f8870bc65same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (9)
- warningshellExec · shell
packages/dsh-re-workbench/lib/index.js:34const out = execFileSync(finder, [names[0]], { encoding: "utf8", timeout: 5000, windowsHide: true }); - warningnetIp · network
packages/dsh-re-workbench/lib/index.js:130const rpc = parseRpc(cfg.idaRpc || "http://127.0.0.1:13337"); - warningfsWrite · files
packages/dsh-re-workbench/lib/index.js:199fs.writeFileSync(targetFile, abs, "utf8"); - warningchildProcess · code-exec
packages/dsh-re-workbench/mcp/server.js:146const child = spawn(env.python, args, { - warningchildProcess · code-exec
packages/dsh-re-workbench/mcp/server.js:202const child = spawn(env.python, args, { - warningshellExec · shell
packages/dsh-re-workbench/mcp/server.js:42const out = execFileSync(finder, [name], { encoding: "utf8", timeout: 5000, windowsHide: true }); - warningnetIp · network
packages/dsh-re-workbench/mcp/server.js:199`[dsh-re-workbench] gui mode (ida-pro-mcp -> ${process.env.RE_IDA_RPC || "http://127.0.0.1:13337"})\n` + - warningchildProcess · code-exec
packages/dsh-thesis-workbench/lib/spss-core.js:62const proc = spawn(`"${pythonBat}" "${scriptPath}"`, { - warningfsWrite · files
packages/dsh-thesis-workbench/lib/spss-core.js:115fs.writeFileSync(pyPath, content, { encoding: "utf8" });
show 3 audit findings
- mediumAgent can self-enable IDA 'unsafe' (DANGEROUS) tools by calling re_open with unsafe:true
packages/dsh-re-workbench/lib/index.js:206re_open is a model-callable tool. Passing unsafe:true sets RE_UNSAFE=1 in the plugin process; mcp/server.js forwards this as --unsafe to idalib_stdio.py, which then registers the functions that ida_pro_mcp marks as DANGEROUS (the upstream file even labels the flag 'DANGEROUS'). The safety gate is therefore controlled by the same principal it is meant to constrain, so the model can silently widen its own capability (upstream unsafe functions typically expose raw script/IDA-API execution inside the host process).
- lowSPSS batch runner uses shell:true with a concatenated command string
packages/dsh-thesis-workbench/lib/spss-core.js:62The interpreter path (SPSS_PATH / SPSS_PYTHON_BAT / plugin config) is interpolated into a string executed by cmd.exe or /bin/sh (shell:true at line 66). A path containing quotes or shell metacharacters would break out of the quoting and run unintended commands, or silently launch a different binary. No model-supplied value reaches this string (scriptPath is a generated temp file name), so exploitation requires control of the operator's config/environment — hence low, not high.
- lowUnescaped apostrophes in model-supplied paths are interpolated into SPSS GET FILE syntax
packages/dsh-thesis-workbench/lib/spss-core.js:153pyStr() only normalises backslashes (line 144); it does not escape single quotes. A sav_path / data_file such as x.sav'. DESCRIPTIVES VARIABLES=All. ' closes the quoted literal and appends arbitrary SPSS syntax inside the read-only data tools. It does not add capability (spss_run already executes arbitrary syntax by design) but it is a weak-validation path in tools advertised as data inspection.
No backdoor or exfiltration found; two concrete gaps: the agent can self-enable IDA 'unsafe' tools, and SPSS is launched via a shell command string.
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-09-30 · activity: Stable
• Repo created: 2026-09-28
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/wxlei2004/dsh-plugins
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 @wxlei2004/dsh-plugins?
@wxlei2004/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.
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 @wxlei2004/dsh-plugins?
Run dsh plugin --profile web add github:wxlei2004/dsh-plugins 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-13 (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.