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
DSH plugin manager that manages plugin registry and lifecycle (create, mount, start, stop, uninstall, configure).
- Plugin archive with source, version, status, config summary
- Full lifecycle management: create/mount/start/stop/uninstall/configure
- Safety: config backup, sandbox precheck, keep data on uninstall
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:jonah791/dsh-agent-plugin-manager#v0.1.1Install method: GitHub · 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.
current (registry 2026-11-17) · 8 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-05 · 8 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
09-24 → 11-05 · 7 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
Based on 1 requirement(s) across 6 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 ×6
✗ 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-agent-plugin-manager@0.1.1 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 |
|---|---|---|---|---|---|
| v0.1.1 | ✗ | ✗ | ○ | ○ | ○ |
v0.1.1github2 failed2026-11-14
https://github.com/jonah791/dsh-agent-plugin-manager
✗dsh 0.2.1-rc.52026-10-31L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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.2.1-rc.32026-10-27L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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.2.1-rc.22026-10-19not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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-17not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
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-11not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@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-09not tested
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@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-29not tested
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@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-26not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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-alpha.22026-09-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.6-alpha.22026-09-20not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
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.6-alpha.12026-09-17not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.5-rc.22026-09-13not tested
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
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.3-alpha.22026-09-09not tested
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@dsh0.1.3-alpha.2 · profile: l3-fullscan
Issued: 2026-09-09 · expires: 2026-09-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.
○prehistory2026-10-04not tested
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-plugin-manager#v0.1.1
ID: dsh-agent-plugin-manager@v0.1.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-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.
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-agent-plugin-manager/?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.
v0.1.1dsh manifestv0.1.1git2026-11-17v0.1.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (3)
- criticalspawnShell · shell
src/profile.ts:222const child = spawn('pnpm', ['install', '--package-import-method=copy'], { cwd: profileDir, shell: true }) - warningfsWrite · files
src/index.ts:159fs.appendFileSync(join(dshHome || process.cwd(), '.plugin-manager-events.log'), '[' + new Date().toISOString() + '] ' + msg + '\n') - warningfsWrite · files
src/index.ts:602fs.appendFileSync(join(dshHome, '.plugin-manager-events.log'), '[' + new Date().toISOString() + '] daemon_restart: ' + args.reason.trim() +
show 4 audit findings
- mediumUnvalidated `profile` parameter is joined into filesystem paths and allows escaping profilesDir
src/index.ts:186The `profile` argument of plugin_mount/plugin_start/plugin_stop/plugin_unmount/plugin_configure is never validated or allow-listed; path.join normalizes '..' sequences, so values such as '../../..' resolve outside profilesDir. If the resolved directory already contains a cordis.patch.yml (e.g. another profile dir or a directory an attacker prepared), mount() then calls packageAddLinkDep() (rewrites that package.json), patchInsert() (appends to that cordis.patch.yml) and installProfile() (spawns `pnpm install` with that directory as cwd), i.e. writes into and executes package installation outsi
- lowpnpm install is spawned with shell: true although the command line is fully static
src/profile.ts:222The command string and arguments are hard-coded constants with no interpolated user input, so no shell injection is demonstrable; shell:true only widens the surface (cmd.exe/shell resolution of `pnpm` from cwd-dependent PATH). cwd is the profile directory selected by callers, so the invoked binary comes from the inherited PATH rather than an absolute path.
- lowplugin_create interpolates the free-text description into a generated TypeScript source file
src/index.ts:116`description` is not escaped before being written into src/index.ts of the new scaffold; a description containing `*/` can close the comment and append arbitrary code to the generated module. Execution is not immediate (the scaffold has no lib/index.js until it is built with tsc and mounted via plugin_mount), so this is a two-step, actor-controlled path rather than a direct RCE; the name is already JSON.stringify-escaped, so only description is affected.
- lowPreflight decision logic is delegated to an absolute-path linked local package (dsh-agent-preflight)
package.jsonrunPreflightCore from `dsh-agent-preflight/core` (imported at src/profile.ts:14) is loaded into the host process and its result gates restarts and rollbacks, but the package lives at a mutable absolute path outside this repository and is not part of the audited artifact, so its behaviour cannot be verified here; anyone able to write that directory changes code running inside the DSH host and the preflight verdict.
No critical RCE: spawn args are fixed; main issue is an unvalidated `profile` path parameter that can escape profilesDir for file writes and pnpm install.
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-12 · activity: Active
• Repo created: 2026-08-17
• Stars: ★ 1 · 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 dsh-agent-plugin-manager?
dsh-agent-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-agent-plugin-manager?
Run dsh plugin --profile web add github:jonah791/dsh-agent-plugin-manager#v0.1.1 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.
