Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Routes all DSH runtime traffic (model requests, web search/fetch, spawned tools) through the Windows system proxy or a custom address, with a one-click header toggle.
- Chat header capsule toggles proxy ON/OFF and doubles as manual re-check
- Settings page shows runtime facts plus PROXIED/DIRECT routing diagnostics and NTLM hints
- Single transport channel via dsh http proxy, avoiding duplicate undici instances
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.
6 samples (roughly every 7 days), 3 of them reconstructed (hollow dots); sampled points, not a daily series
09-18 → 10-29 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
09-23 → 10-29 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-17 → 10-31 · 34 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
09-17 → 10-31 · 34 points
Installation
dsh plugin --profile web add @yanglaofish/dsh-proxy-proInstall method: npm · sandbox install ok, web smoke failed (L5)
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 4 @deepseek-ai/dsh-* packages. raw ranges
>=0.2.0-rc.2 <0.3.0 ×4
✓ Running dsh 0.2.1-rc.5 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.1-rc.5 current | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 2.0.4 | ✗ | · | · | · | · |
| 2.0.3 | · | ✗ | · | · | · |
| 2.0.2 | · | · | ✗ | ✗ | · |
| 2.0.1 | · | · | · | · | ✗ |
| 1.0.10 | · | · | · | · | · |
2.0.4npm1 failed2026-10-31
@yanglaofish/dsh-proxy-pro
✗dsh 0.2.1-rc.5current2026-10-31L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · @yanglaofish/dsh-proxy-pro@2.0.4
ID: dsh-proxy-pro@2.0.4@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.
2.0.3npm1 failed2026-10-26
@yanglaofish/dsh-proxy-pro
✗dsh 0.2.1-rc.32026-10-26L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · @yanglaofish/dsh-proxy-pro@2.0.3
ID: dsh-proxy-pro@2.0.3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
2.0.2npm2 failed2026-10-19
@yanglaofish/dsh-proxy-pro
✗dsh 0.2.1-rc.22026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @yanglaofish/dsh-proxy-pro@2.0.2
ID: dsh-proxy-pro@2.0.2@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-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · @yanglaofish/dsh-proxy-pro@2.0.2
ID: dsh-proxy-pro@2.0.2@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
2.0.1npm1 failed2026-10-11
@yanglaofish/dsh-proxy-pro
✗dsh 0.2.1-alpha.22026-10-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @yanglaofish/dsh-proxy-pro@2.0.1
ID: dsh-proxy-pro@2.0.1@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.
1.0.10npm3 failed2026-10-09
@yanglaofish/dsh-proxy-pro
✗dsh 0.2.0-rc.22026-10-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · @yanglaofish/dsh-proxy-pro@1.0.10
ID: dsh-proxy-pro@1.0.10@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: npm · @yanglaofish/dsh-proxy-pro@1.0.10
ID: dsh-proxy-pro@1.0.10@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.
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @yanglaofish/dsh-proxy-pro@1.0.10
ID: dsh-proxy-pro@1.0.10@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.
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-proxy-pro/?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.
v2.0.4dsh manifest2.0.4npm2026-11-012.0.4same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningnetIp · network
lib/client.js:514placeholder: "http://127.0.0.1:7890", - warningchildProcessImport · code-exec
lib/index.js:30import { execFile } from 'node:child_process' - warningnetIp · network
lib/index.js:96customUrl: volatile(z.string().default('http://127.0.0.1:7890')), - warningshellExec · shell
lib/proxy-core.js:192const result = await execFile('reg', ['query', PROXY_REG_KEY, '/v', valueName], { - warningnetIp · network
lib/tool-schemas.js:126description: 'Proxy address for mode "custom", e.g. http://127.0.0.1:7890 (bare host:port also accepted). Pass an empty string to clear it.'
show 1 audit findings
- lowModel-callable proxy_config/proxy_set can repoint the whole runtime's egress without a confirmation step
lib/index.jsThe tools are advertised (also in the system-prompt section) as an agent capability and persist immediately. If the model is steered by untrusted fetched content, it can set an arbitrary http(s) proxy and re-route model API traffic, tool traffic and spawned processes through it, exposing bearer keys/credentials to the proxy operator. It requires the model to choose to call the tool, so no unattended exploitation path exists.
Static flags are shape-only: reg.exe runs with constant args, the panel HTTP API is loopback-fenced, and every outbound fetch is the advertised proxy diagnostic — no reachable critical/high risk.
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-10-27 · activity: Active
• Repo created: 2026-09-16
• Stars: ★ 8 · Forks: 1
• 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-proxy-pro?
dsh-proxy-pro 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-proxy-pro?
Run dsh plugin --profile web add @yanglaofish/dsh-proxy-pro 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-01 (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.