Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Toolbox plugin for dsh managing sessions, trash, subdirectories, search, presets, config, with scheduled heartbeat and long-message collapse.
- Session and trash management
- Subdirectory, search, preset, config tools
- Scheduled heartbeat & long-message collapse
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 dsh-toolbox-webInstall method: npm · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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.
7 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-11 · 7 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-11 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-19 → 11-15 · 77 points
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
08-19 → 11-16 · 78 points
Verification & Compatibility
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
Based on 1 requirement(s) across 2 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 ×2
✗ Running dsh 0.2.2-rc.3 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-toolbox-web@0.1.29 0.2.2-rc.3 (the exemption lives in the local profile; this site does not assume one)
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin \ dsh | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 0.1.29 | · | · | ✗ | ✗ | ✗ |
| 0.1.28 | · | · | · | · | · |
| 0.1.26 | · | · | · | · | · |
| 0.1.20 | · | · | · | · | · |
| 0.1.19 | · | · | · | · | · |
0.1.29npm10 failed2026-11-14
dsh-toolbox-web
✗dsh 0.2.1-rc.22026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-toolbox-web@0.1.29
ID: dsh-toolbox-web@0.1.29@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
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-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-toolbox-web@0.1.29
ID: dsh-toolbox-web@0.1.29@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
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-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-toolbox-web@0.1.29
ID: dsh-toolbox-web@0.1.29@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
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-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-toolbox-web@0.1.29
ID: dsh-toolbox-web@0.1.29@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
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-29L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-toolbox-web@0.1.29
ID: dsh-toolbox-web@0.1.29@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
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-25L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-toolbox-web@0.1.29
ID: dsh-toolbox-web@0.1.29@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
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-24L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-toolbox-web@0.1.29
ID: dsh-toolbox-web@0.1.29@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
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-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-toolbox-web@0.1.29
ID: dsh-toolbox-web@0.1.29@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
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-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-toolbox-web@0.1.29
ID: dsh-toolbox-web@0.1.29@dsh0.1.6-alpha.1 · profile: l3-fullscan
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-toolbox-web@0.1.29
ID: dsh-toolbox-web@0.1.29@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.28npm2026-09-16
dsh-toolbox-web
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.1.26npm1 failed2026-09-13
dsh-toolbox-web
✗dsh 0.1.5-rc.22026-09-13L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-toolbox-web@0.1.26
ID: dsh-toolbox-web@0.1.26@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.20npm1 failed2026-09-11
dsh-toolbox-web
✗dsh 0.1.3-alpha.22026-09-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-toolbox-web@0.1.20
ID: dsh-toolbox-web@0.1.20@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.19npm1 failed2026-09-06
dsh-toolbox-web
✗dsh 0.1.3-alpha.12026-09-06L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · dsh-toolbox-web@0.1.19
ID: dsh-toolbox-web@0.1.19@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
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-toolbox-web/?ref=badge)``[](https://www.dsh.so/artifact/dsh-toolbox-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.
v0.1.29dsh manifest0.1.29npm2026-11-170.1.29same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningfsWrite · files
index.js:496fs.appendFileSync( - warningfsWrite · files
index.js:504fs.appendFileSync(path.join(PLUGIN_STATE_DIR, "search-debug.log"), new Date().toISOString() + " ERROR " + String(err) + "\n"); - warningfsWrite · files
index.js:709fs.writeFileSync(tmp, content, "utf-8"); - warningfsWrite · files
lib/config.js:64fs.writeFileSync(tmp, JSON.stringify(keep, null, 2), "utf-8"); - warningfsWrite · files
lib/config.js:77fs.writeFileSync(tmp, JSON.stringify(current, null, 2), "utf-8"); - warningfsWrite · files
lib/config.js:80fs.chmodSync(CONFIG_PATH, 0o600); - warningfsWrite · files
lib/embed.js:41fs.writeFileSync(tmp, JSON.stringify(idx), "utf-8"); - warningfsWrite · files
lib/messages.js:172fs.writeFileSync(file, out); - warningfsWrite · files
lib/messages.js:231fs.writeFileSync(file, outText); - warningfsWrite · files
lib/presets.js:66fs.writeFileSync(tmp, content, "utf-8"); - warningfsWrite · files
lib/search.js:252fs.writeFileSync(PROFILE_PATCH, text, "utf-8"); - warningfsWrite · files
lib/search.js:269fs.writeFileSync(PROFILE_PATCH, out.join("\n"), "utf-8");
show 3 audit findings
- hightrash.purge / trash.restore pass a caller-supplied path straight to fs without trash-root containment
index.js:883Any caller that can invoke the dsh-toolbox namespace can send entryDir="/workspace" (or "/") and recursively delete it inside the host process; no check ties entryDir to TRASH_ROOT. The sibling handlers are equally unguarded: trash.restore -> restoreTrashEntry() reads <entryDir>/meta.json and moves <entryDir>/data to the arbitrary meta.sourcePath (lib/trash.js), and trash.view reads any directory that happens to contain session.jsonl.zstd. The plugin's own client always sends a listTrash() path, but nothing enforces that.
- mediumWorkspace subdir operations join unvalidated names to WORKSPACE_ROOT (../ traversal)
lib/workspace.js:37name/oldName/newName arrive as plain typert wire params and are joined without normalization or containment checks, so a value such as "../../etc" or ".." escapes /workspace: workspace.create makes directories outside the workspace, workspace.rename moves any existing directory to an attacker-chosen path, and workspace.delete/workspace.copy relocate or copy arbitrary trees (delete goes through trashItem, i.e. a rename of the target into the plugin trash).
- lowclient.js is published and loaded by the web UI but was not part of the audited source set
package.json:44The package ships and exports a browser bundle (also declared in dsh.client.inject) that drives every RPC above and renders session/message content. It was not present in the harvested 15 files, so any DOM/XSS or unsafe-render sink there is outside this audit and the residual risk on the client side is unknown.
RPC handlers trash.purge/trash.restore and workspace.* forward caller-supplied paths to fs without containment checks, allowing arbitrary directory deletion/move; the remaining modules are defensively written.
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-15 · activity: Stable
• Repo created: 2026-08-15
• Stars: ★ 4 · 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-toolbox-web?
dsh-toolbox-web is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
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-toolbox-web?
Run dsh plugin --profile web add dsh-toolbox-web in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run yet.
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.
