Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
A toolkit for DSH plugin developers: Alt+hover UI element locator, a bundled experience library, and dev-mode checklists injected into the AI workflow.
- Alt+hover any UI element to see its name and full path, copy in one click
- Ships 23 field-tested DSH plugin pitfalls, indexed into the AI assistant's prompt
- Injects pre-work self-checks and requirement-alignment gates into the AI workflow
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.
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); the npm pair from every snapshot.
current (registry 2026-11-10) · 5 samples (roughly every 7 days), 1 of them reconstructed (hollow dots); sampled points, not a daily series
10-06 → 11-05 · 5 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-15 → 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
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:eighteentang/dsh-plugin-dev-tools#v1.3.0Install method: GitHub · sandbox install ok, web smoke failed (L5)
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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.2-rc.1 current | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| v1.6.4 | · | · | · | · | · |
| v1.3.0 | ✗ | ✗ | ✗ | ✗ | ✗ |
v1.6.4github2026-11-09
https://github.com/eighteentang/dsh-plugin-dev-tools
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v1.3.0github5 failed2026-11-05
https://github.com/eighteentang/dsh-plugin-dev-tools
✗dsh 0.2.2-rc.1current2026-11-05L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/eighteentang/dsh-plugin-dev-tools#v1.3.0
ID: dsh-plugin-dev-tools@v1.3.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
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-31L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/eighteentang/dsh-plugin-dev-tools#v1.3.0
ID: dsh-plugin-dev-tools@v1.3.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
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-26L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/eighteentang/dsh-plugin-dev-tools#v1.3.0
ID: dsh-plugin-dev-tools@v1.3.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
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-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/eighteentang/dsh-plugin-dev-tools#v1.3.0
ID: dsh-plugin-dev-tools@v1.3.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
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-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/eighteentang/dsh-plugin-dev-tools#v1.3.0
ID: dsh-plugin-dev-tools@v1.3.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-plugin-dev-tools@v1.6.4@dsh0.2.2-rc.1 (l3-fullscan)
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-plugin-dev-tools/?ref=badge)``[](https://www.dsh.so/artifact/dsh-plugin-dev-tools/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-dev-tools/?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 medium (authoritative when present) → overall medium.
v1.6.4dsh manifestv1.6.4git2026-11-11v1.6.4same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- criticalspawnShell · shell
acceptance.js:509? spawnSync(command, { shell: true, cwd: workdir, timeout: budget, encoding: 'utf8', windowsHide: true, maxBuffer: 8 * 1024 * 1024 }) - criticalshellExec · shell
client.js:1256if (exec('copy') === true) return 'copied'; - warningchildProcess · code-exec
acceptance.js:509? spawnSync(command, { shell: true, cwd: workdir, timeout: budget, encoding: 'utf8', windowsHide: true, maxBuffer: 8 * 1024 * 1024 }) - warningchildProcess · code-exec
acceptance.js:510: spawnSync('powershell.exe', ['-NoProfile', '-NonInteractive', '-ExecutionPolicy', 'Bypass', '-Command', command], { - warningshellExec · shell
acceptance.js:134const out = execFileSync('git', ['-C', root, 'rev-parse', '--show-toplevel'], { - warningshellExec · shell
acceptance.js:152const out = execFileSync('git', ['-C', top, 'status', '--porcelain', '--untracked-files=all'], { - warningchildProcess · code-exec
app-control.js:577` const child = spawn(${JSON.stringify(appPath)}, [], { detached: true, stdio: 'ignore' });`, - warningchildProcess · code-exec
app-control.js:584const helper = spawn(process.execPath, ['-e', helperScript], { detached: true, stdio: 'ignore' }); - warningshellExec · shell
app-control.js:126const out = execFileSync('powershell', [ - warningshellExec · shell
app-control.js:560" try { execFileSync('taskkill', ['/PID', String(shellPid), '/F'], { stdio: 'ignore' }); log('taskkill ok'); }", - warningnetIp · network
app-control.js:243const url = new URL(req.url ?? '/', `http://127.0.0.1:${CONTROL_PORT}`); - warningnetIp · network
app-control.js:631logLine(`控制接口就绪 http://127.0.0.1:${CONTROL_PORT}/dev-tools/`);
show 2 audit findings
- mediumOrigin whitelist trusts every localhost port, so any locally-served page can quit/restart the host and toggle dev mode
app-control.js:200The only browser-side gate is 'the page happens to be served from a loopback host on any port'. Any local dev server, docs server, or attacker-influenced page on http://127.0.0.1:<port> passes; combined with the echoed Access-Control-Allow-Origin and the 204 OPTIONS handler it can, without user action, POST /dev-tools/quit (process.exit(0) after 1.5 s: host dies, DSH shows the crash-recovery dialog), POST /dev-tools/restart (spawns a detached helper that runs taskkill /PID <shell> /F and relaunches the app), and POST /dev-tools/dev-mode {enabled:true}, which registers the command-executing too
- mediumrun_verification executes model-supplied commands via PowerShell with -ExecutionPolicy Bypass and persists output
acceptance.js:551The tool's whole contract is 'run this string', with no allowlist, no sandbox and a bypassed PowerShell execution policy; any text that reaches the model (a README, a fetched file, a pasted log — i.e. prompt injection) can turn run_verification into a general shell at the user's privilege level. Reachability is gated only by 'dev mode is on', and dev mode can be flipped from any localhost-origin page via POST /dev-tools/dev-mode (see the other finding), so the capability can be enabled without the user touching the toggle. Each run also writes command line, cwd, output tails and hashes into ~/
Loopback HTTP control server with a coarse origin whitelist lets any locally-served page kill/restart the host and flip dev mode, which enables an unrestricted model-driven shell tool.
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-11-06 · activity: Active
• Repo created: 2026-09-26
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 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 @eighteentang/dsh-plugin-dev-tools?
@eighteentang/dsh-plugin-dev-tools 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 @eighteentang/dsh-plugin-dev-tools?
Run dsh plugin --profile web add github:eighteentang/dsh-plugin-dev-tools#v1.6.4 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed 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-11 (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.