Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
A DSH plugin marketplace plugin that auto-updates and lets you quickly search for useful plugins.
- Auto-updates plugin data
- Quick plugin search
- Web UI for browsing
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:cyber-moshen/dsh-plugin-market#v0.3.0Install method: GitHub · runtime verified (L5) · 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.
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-08 · 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-08 · 6 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 2 @deepseek-ai/dsh-* packages. raw ranges
* ×2
✓ Running dsh 0.2.2-rc.3 is within the declared range — install is not blocked by version.
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.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 |
|---|---|---|---|---|---|
| v0.3.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
v0.3.0github✓ 16 runtime-verified2026-11-14
https://github.com/cyber-moshen/dsh-plugin-market
✓dsh 0.2.2-rc.12026-11-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-07 · expires: 2026-11-14
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
active in loader tree (150 entries)
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-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
active in loader tree (150 entries)
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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
active in loader tree (150 entries)
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-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
active in loader tree (150 entries)
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-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
View checks & evidence
active in loader tree (150 entries)
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (151 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/cyber-moshen/dsh-plugin-market#v0.3.0
ID: dsh-plugin-market-5@v0.3.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
active in loader tree (150 entries)
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-market-5/?ref=badge)``[](https://www.dsh.so/artifact/dsh-plugin-market-5/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-market-5/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-market-5/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-market-5/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-plugin-market-5/?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.3.0dsh manifestv0.3.0git2026-11-14v0.3.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalspawnShell · shell
lib/host.js:763if (binInfo.kind === 'cmd') return spawn(binInfo.bin, args, { ...common, shell: true }) - warningchildProcess · code-exec
lib/host.js:194child = spawn(process.execPath, - warningchildProcess · code-exec
lib/host.js:365const out = spawnSync(which, ['dsh'], { encoding: 'utf8' }) - warningchildProcess · code-exec
lib/host.js:754spawn('taskkill', ['/pid', String(child.pid), '/T', '/F'], { stdio: 'ignore' })
show 4 audit findings
- highCommand injection: request-supplied binPath/target reach spawn() with shell:true
lib/host.js:762launchTask() builds binInfo directly from the request body: `(explicitBin && explicitBin.trim()) ? { bin: explicitBin.trim(), kind: classifyBin(explicitBin.trim()) } : locateDshCli()` (line 804), where explicitBin is body.binPath. classifyBin() returns 'cmd' for any string ending in .cmd/.bat, so a POST such as {method:'install', source:'x', binPath:'true; id #.cmd'} makes the host execute `sh -c "true; id #.cmd plugin --profile web add x -w"` (on Windows the resolved dsh.cmd has the same shell:true path, and the unquoted `target` argument is equally injectable). Arbitrary OS commands run with
- mediuminstall/update endpoint runs `dsh plugin add|update` with an arbitrary package spec from the request
lib/host.js:818The route derives target straight from the body (`body.source` for install, `body.pkg` otherwise) and only sanitises the profile name (isSafeProfile). For installs into 'web' the single guard is assessSource(), which refuses only github:* sources that look like a full app, and is skipped entirely when body.skipCheck is true; any npm name is accepted. The resulting pnpm install executes the package's lifecycle scripts, so anyone who can reach POST /api/dsh-plugin-market gets code execution in the DSH process, and the route itself has no auth/CSRF check.
- mediumCatalog and package metadata are fetched through third-party GitHub proxies without integrity checks
lib/host.js:51loadCatalog(), queryLatestVersion(), auditBundleFanout() and assessSource() all read data/plugins.json and package.json over ghproxy.net / gh-proxy.com / ghfast.top / raw.githubusercontent.com in order, with no signature or hash check and no pinning to a commit (HEAD). A compromised or malicious mirror can serve a doctored catalog, so the 'official' market UI advertises attacker-chosen repositories, and can also flip the two safety checks (app-like detection and bundle fan-out warning) that are supposed to protect installs.
- lowGitHub token stored in plaintext and echoed (last 4 chars) to API clients
lib/host.js:299saveConfig() writes the GitHub token in clear text to $DSH_HOME/.dsh-plugin-market-config.json (configPath(), line 106), and the list/config handlers return tokenTail = token.slice(-4) plus environmentInfo() (dshHome, node path, dshBin) to any caller of the route. The token also becomes visible to anyone with read access to that file or a backup.
Marketplace plugin runs package installs via the dsh CLI; request-controlled binPath/target reach a shell:true spawn, and the catalog comes from unchecked third-party mirrors.
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-15 · activity: Inactive
• Repo created: 2026-08-14
• Stars: ★ 2 · Forks: 2
• 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-market?
dsh-plugin-market 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-market?
Run dsh plugin --profile web add github:cyber-moshen/dsh-plugin-market#v0.3.0 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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-14 (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.