Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Routes requests to specialized AI agents with per-agent model binding, account pool health routing, and real-time usage stats.
- Binds independent models to custom vision/translation/voice agents
- Account pool health routing with real-time usage statistics
- One-click login for multimodal accounts
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:peterwangze/dsh-agent-router#v0.8.2Install method: GitHub · runtime verified (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.
current (registry 2026-11-17) · 11 samples (roughly every 7 days), 6 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-13 · 11 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-13 · 10 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 |
|---|---|---|---|---|---|
| v0.8.2 | ✓ | · | · | · | · |
| v0.8.1 | · | · | · | · | · |
| v0.7.1 | · | ✗ | ✗ | ✗ | · |
| v0.6.2 | · | · | · | · | · |
| v0.6.1 | · | · | · | · | · |
v0.8.2github✓ 1 runtime-verified2026-11-17
https://github.com/peterwangze/dsh-agent-router
✓dsh 0.2.2-rc.3current2026-11-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/peterwangze/dsh-agent-router#v0.8.2
ID: dsh-agent-router@v0.8.2@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-17 · expires: 2026-11-24
View checks & evidence
active in loader tree (207 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.8.1github2026-11-09
https://github.com/peterwangze/dsh-agent-router
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.7.1github3 failed2026-11-05
github:peterwangze/dsh-agent-router#v0.7.1
✗dsh 0.2.2-rc.12026-11-05L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · github:peterwangze/dsh-agent-router#v0.7.1#v0.7.1
ID: dsh-agent-router@v0.7.1@dsh0.2.2-rc.1 · profile: l5-web-smoke
Issued: 2026-11-05 · expires: 2027-02-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.52026-10-31L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/peterwangze/dsh-agent-router#v0.7.1
ID: dsh-agent-router@v0.7.1@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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/peterwangze/dsh-agent-router#v0.7.1
ID: dsh-agent-router@v0.7.1@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.
v0.6.2github2026-10-23
https://github.com/peterwangze/dsh-agent-router
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.6.1github2026-10-21
https://github.com/peterwangze/dsh-agent-router
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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-router/?ref=badge)``[](https://www.dsh.so/artifact/dsh-agent-router/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-agent-router/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-agent-router/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-agent-router/?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 high; dynamic low (authoritative when present) → overall low.
v0.8.1dsh manifestv0.8.1git2026-11-17v0.8.2version moved onsuspicious · gitVet is an AST static scan (npm artifact or git source).
show static findings (1)
- warningnetIp · network
.governance/tmp-repro-014.mjs:3const BASE = 'http://127.0.0.1:3080'
show 2 audit findings
- lowInstaller clones and loads the unpinned main branch with no integrity verification
install.sh:10The documented one-liner piped to sh executes whatever is on the default branch at install/update time (git clone/fetch/pull of $REPO_URL) and then links it into profiles/node_modules and the host-plane cordis.patch.yml. Compromise of the GitHub repo or account, or a malicious maintainer push, yields code execution inside DSH without any hash/commit pinning or signature check. Requires a real precondition (repo/account compromise), hence low.
- lowDev forensic script calls the local DSH API and creates a blank session, but is not shipped or loaded
.governance/tmp-repro-014.mjs:3This is the construct behind the static scan's fetch warning: it POSTs JSON-RPC to 127.0.0.1:3080, creates a blank session and switches presets. It is absent from package.json `files`, lives under .governance/ and is imported by nothing, so it never runs as part of the plugin; impact is limited to a developer manually executing it against their own local instance.
Only host-ABI glue, RPC descriptors, image cache and installer were harvested; no reachable vulnerability found, but the runtime handlers (index/service/client/oauth-llm) were missing.
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-09 · activity: Active
• Repo created: 2026-08-15
• Stars: ★ 5 · 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-router?
dsh-agent-router 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-router?
Run dsh plugin --profile web add github:peterwangze/dsh-agent-router#v0.8.1 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-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.
