Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
In-web plugin manager for DeepSeek Harness: categorized list, tags, preset switching, marketplace, import/export, balance.
- Categorized plugin list with tags
- One-click preset switching
- Plugin marketplace and import/export
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:kkkkkklze/dsh-plugin-managerInstall method: GitHub · sandbox install ok, web smoke failed (L5)
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), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-03 · 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-01 → 11-03 · 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
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| ab17c3 | ✗ | · | · | · | · |
| 86adc8 | · | ✗ | ✗ | ✗ | ✗ |
ab17c3github1 failed2026-11-17
https://github.com/kkkkkklze/dsh-plugin-manager
✗dsh 0.2.2-rc.3current2026-11-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager#ab17c3b5f972c4f4ebb1a6c64026338ddf080c20
ID: dsh-plugin-manager-13@ab17c3b5f972c4f4ebb1a6c64026338ddf080c20@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-17 · expires: 2026-11-24
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
86adc8github◐ 1 testing17 failed2026-11-14
https://github.com/kkkkkklze/dsh-plugin-manager
✗dsh 0.2.2-rc.12026-11-06L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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-rc.52026-11-01L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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-rc.32026-10-27L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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-rc.22026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@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: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@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: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@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: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@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-30L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
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: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@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-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
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.6-alpha.22026-09-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@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: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@dsh0.1.6-alpha.1 · profile: l4-sandbox
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.
✗dsh 0.1.5-rc.22026-09-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
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-07L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.2-rc.12026-09-05L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager#86adc8
ID: dsh-plugin-manager-13@86adc8@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
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-06L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@dsh0.1.2-alpha.1 · profile: l3-fullscan
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.
◐dsh 0.1.1-rc.22026-08-28L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.1.1-rc.2
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager#86adc8
ID: dsh-plugin-manager-13@86adc8@dsh0.1.1-rc.2 · profile: l3-fullscan
Issued: 2026-08-28 · expires: 2026-09-04
View checks & evidence
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.
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/kkkkkklze/dsh-plugin-manager (version unstated)
ID: dsh-plugin-manager-13@86adc8@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.
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-manager-13/?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 low (authoritative when present) → overall low.
v0.1.0dsh manifest0.1.0git2026-11-170.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (8)
- criticalshellExec · shell
manager.js:522exec(arg, { timeout: 180000, maxBuffer: 8 * 1024 * 1024, windowsHide: true }, (error, stdout, stderr) => { - criticalshellExec · shell
manager.js:542exec(arg, { timeout: 180000, maxBuffer: 8 * 1024 * 1024, windowsHide: true }, (error, stdout, stderr) => { - warningfsWrite · files
manager.js:53await fs.writeFile(statePath, JSON.stringify(state, null, 2), 'utf8') - warningfsWrite · files
manager.js:93await fs.writeFile(tagsPath, yaml.dump(tags, { noRefs: true }), 'utf8') - warningfsWrite · files
manager.js:98await fs.writeFile(rollbackPath, JSON.stringify(previousState, null, 2), 'utf8') - warningfsWrite · files
verify.mjs:92await fs.writeFile(patchPath, sample + '\n', 'utf8') - warningfsWrite · files
verify.mjs:93await fs.writeFile(path.join(tmp, 'plugin-presets.yml'), '日常:\n description: 默认\n plugins: [tools, bash]\n', 'utf8') - warningfsWrite · files
verify.mjs:267await fs.writeFile(statePathTmp, JSON.stringify({ inserted: { 'pm-manager': { name: 'dsh-plugin-manager' } }, overrides: { ghost: { name: 'g
show 4 audit findings
- lowReads the plaintext DEEPSEEK_API_KEY from .credentials.yaml and sends it to api.deepseek.com on every UI load
manager.jsThe key is read server-side from the shared dsh credentials file and placed in an Authorization header. The destination is hardcoded to the official vendor endpoint and the key is never returned to the browser, so no exfiltration was found; the residual risk is that any future change to the URL, a proxy env var, or a compromised TLS path would expose a live API key, and the browser half triggers this read automatically on page load and every 60s.
- lowchild_process.exec builds a shell string; the repo segment is allowlisted but the profile segment is interpolated unvalidated
manager.jsexec runs through /bin/sh, so metacharacters matter. The user-controlled segment is defended: validRepo() enforces /^[A-Za-z0-9_.-]+\/[A-Za-z0-9_.-]+$/, length<=200 and no '..', which excludes ; & | $ ` spaces and extra slashes, and opBatchMarketInstall filters its list the same way — so this is defense, not injection. The profile segment instead comes from path.basename(path.dirname(patchPath)) with no validation; it is only attacker-influenced if the profile directory itself is named with shell metacharacters, which is not realistic. No reachable injection path was demonstrated.
- lowApproval gate fails open when the approval service is unavailable, allowing unapproved plugin installs
index.js:63All mutating tools (plugin_add, plugin_market_install, plugin_stop_self, presets...) skip the human-approval step whenever ctx.get('approval') returns null or throws, or when exec.agent is absent. In that state an agent that is prompt-injected could install and enable a GitHub repo (`dsh plugin add github:...`) that executes build/install code, without any confirmation. Requires the approval service to be missing from the harness.
- lowBrowser gateway path calls the same mutating operations with no approval gating
client-bundle.jsindex.js wraps every mutating agent tool in requireApproval, but the web half invokes the same manager operations (marketInstall, batchInstall, stopSelf, removeRow, switchPreset) through the remote service, which shells out (`dsh plugin add github:<repo>`) and rewrites cordis.patch.yml. So the plugin's own stated safety layer (M4) only covers the agent path; anything that can reach the dsh /api remote surface can install third-party code. This is the plugin's intended interactive UI behavior and remote.js was not available for review, so the concrete exposure depends on dsh's own auth/CORS mod
Static criticals are refuted: shell exec is gated by a strict owner/repo allowlist, and the credential read goes only to the official DeepSeek API; remaining issues are low-severity hardening notes.
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-18 · activity: Inactive
• Repo created: 2026-08-15
• Stars: ★ 2 · Forks: 0
• Health: Inactive — no commit in 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-plugin-manager?
dsh-plugin-manager 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-plugin-manager?
Run dsh plugin --profile web add github:kkkkkklze/dsh-plugin-manager 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-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.
