Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
A bundle of local DSH web-profile plugins: Web UI tweaks, model tiering, loop guard, Chrome DevTools MCP tools, and cross-agent bridging.
- Web UI tweaks: copy session ID/path, collapse groups, open in VS Code
- Model ladder adds a ⚡high slot forcing high-tier model, then falls back
- Exposes Chrome DevTools MCP tools and bridges live DSH sessions to Codex
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.
5 samples (roughly every 1 days), 3 of them reconstructed (hollow dots); sampled points, not a daily series
10-02 → 10-19 · 5 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-07 → 10-19 · 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:sun603/dsh-setupInstall method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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 |
|---|---|---|---|---|---|
| a24991 | · | · | · | · | · |
| 057109 | ○ | ○ | ○ | ○ | ○ |
a24991local2026-09-23
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
057109github○ 11 ecosystem plugin2026-11-05
https://github.com/sun603/dsh-setup
○dsh 0.2.2-rc.1current2026-11-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/sun603/dsh-setup (version unstated)
ID: dsh-setup@057109@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-setup@a24991@dsh0.1.7-rc.1 (l3-fullscan)
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-rc.52026-10-31Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/sun603/dsh-setup (version unstated)
ID: dsh-setup@057109@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-setup@a24991@dsh0.1.7-rc.1 (l3-fullscan)
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-rc.32026-10-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/sun603/dsh-setup (version unstated)
ID: dsh-setup@057109@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-setup@a24991@dsh0.1.7-rc.1 (l3-fullscan)
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-rc.22026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/sun603/dsh-setup (version unstated)
ID: dsh-setup@057109@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-setup@a24991@dsh0.1.7-rc.1 (l3-fullscan)
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-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/sun603/dsh-setup (version unstated)
ID: dsh-setup@057109@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-setup@a24991@dsh0.1.7-rc.1 (l3-fullscan)
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-10Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/sun603/dsh-setup (version unstated)
ID: dsh-setup@057109@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-setup@a24991@dsh0.1.7-rc.1 (l3-fullscan)
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-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/sun603/dsh-setup (version unstated)
ID: dsh-setup@057109@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-setup@a24991@dsh0.1.7-rc.1 (l3-fullscan)
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-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/sun603/dsh-setup (version unstated)
ID: dsh-setup@057109@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-setup@a24991@dsh0.1.7-rc.1 (l3-fullscan)
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-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/sun603/dsh-setup (version unstated)
ID: dsh-setup@057109@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-setup@a24991@dsh0.1.7-rc.1 (l3-fullscan)
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.12026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/sun603/dsh-setup (version unstated)
ID: dsh-setup@057109@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-setup@a24991@dsh0.1.7-rc.1 (l3-fullscan)
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-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/sun603/dsh-setup (version unstated)
ID: dsh-setup@057109@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-setup@a24991@dsh0.1.7-rc.1 (l3-fullscan)
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.
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-setup/?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.
—a454a9229f12git2026-11-05a454a9229f12same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningchildProcess · code-exec
plugins/dsh-codex-bridge/lib/index.js:245child = spawn(bin, ['queue', '--thread', threadId, '--message', text], { stdio: ['ignore', 'ignore', 'pipe'] }) - warningnetIp · network
plugins/dsh-codex-bridge/lib/index.js:403return new URL(req.url || '', 'http://127.0.0.1').searchParams - warningnetIp · network
plugins/dsh-codex-bridge/lib/index.js:405return new URL('http://127.0.0.1/').searchParams - warningnetIp · network
plugins/dsh-codex-bridge/mcp/server.mjs:24const BASE_URL = (process.env.DSH_BRIDGE_URL || 'http://127.0.0.1:3080').replace(/\/+$/, '') - warningnetIp · network
plugins/dsh-model-ladder/lib/index.js:283const url = new URL(req.url || '', 'http://127.0.0.1')
show 3 audit findings
- mediumcodex-bridge API is unauthenticated by default (token empty), exposing agent control and transcripts to any loopback caller
plugins/dsh-codex-bridge/lib/index.js:57With the shipped default the guard only checks remoteAddress; token check is skipped when cfg.token is ''. Any local process (or a browser page reaching 127.0.0.1, e.g. via DNS rebinding, subject to content-type preflight limits) can list sessions, read full transcripts via /history, create new sessions with an arbitrary cwd and prompt text (/prompt), cancel/adopt sessions, and — if the operator later enables control.approvals/questions — resolve pending tool approvals through /decide without a human. This lets a local foothold inject instructions into an agent that has tool access.
- mediumChrome MCP plugin defaults to the user's real Chrome profile, giving agents the logged-in browser
plugins/dsh-chrome-devtools-mcp/lib/index.js:14Unless DSH_CHROME_DEVTOOLS_BROWSER_URL / DSH_CHROME_DEVTOOLS_USER_DATA_DIR is set, the spawned chrome-devtools-mcp server launches Chrome against the user's existing profile directory (Profile 2), i.e. with all logged-in cookies and sessions. Any DSH agent session that can call mcp__chrome-devtools__* tools — including one driven by untrusted page content or, per the finding above, by an injected prompt — can navigate and act inside authenticated accounts. The tab-guard only isolates sessions from each other; it does not restrict what the shared authenticated profile exposes.
- lowchrome-devtools-mcp is fetched from npm at runtime via npx -y with an env-overridable binary
plugins/dsh-chrome-devtools-mcp/lib/index.js:16Each start resolves and executes the npm package chrome-devtools-mcp@<DSH_CHROME_DEVTOOLS_MCP_VERSION||1.9.0> (plus its transitive dependencies) without an integrity hash, and the executable itself is chosen via DSH_CHROME_DEVTOOLS_MCP_COMMAND. Whoever controls the environment or the npm resolution path (registry compromise, poisoned npx cache) gets code execution in the DSH host process tree. Requires an environment/registry precondition, so severity is low here.
Loopback guards are real, but codex-bridge ships unauthenticated by default and the Chrome MCP plugin drives the user's logged-in Chrome profile.
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-24 · activity: Stable
• Repo created: 2026-09-23
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/sun603/dsh-setup
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 @sun603/dsh-setup?
@sun603/dsh-setup is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 @sun603/dsh-setup?
Run dsh plugin --profile web add github:sun603/dsh-setup in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-05 (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.