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
Controls DSH's outbound proxy at runtime with three sources (built-in env, system, manual), applying changes instantly without restart.
- Three proxy sources: built-in env, Windows system proxy, or manual
- Changes apply on the next request with no restart required
- Covers fetch, web fetch and subprocesses; loopback always direct
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:Joker-Principal/dsh-proxy-controlInstall 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.
7 samples (roughly every 7 days), 1 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
10-04 → 11-16 · 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-12 → 11-16 · 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
○ 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 |
|---|---|---|---|---|---|
| eb84c3 | ○ | ✗ | ✗ | ✗ | ✗ |
| 164a29 | ✓ | · | · | · | · |
eb84c3github8 failed2026-11-15
https://github.com/Joker-Principal/dsh-proxy-control
○dsh 0.2.2-rc.3current2026-11-15not tested
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/Joker-Principal/dsh-proxy-control (version unstated)
ID: dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-15 · expires: 2026-11-22
View checks & evidence
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
inventory probe failed (rpc-error) — inconclusive, not a plugin verdict (reinterpreted 2026-11-17)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.2-rc.12026-11-04L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/Joker-Principal/dsh-proxy-control (version unstated)
ID: dsh-proxy-control@eb84c3@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
View checks & evidence
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
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/Joker-Principal/dsh-proxy-control (version unstated)
ID: dsh-proxy-control@eb84c3@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Joker-Principal/dsh-proxy-control (version unstated)
ID: dsh-proxy-control@eb84c3@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
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-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Joker-Principal/dsh-proxy-control (version unstated)
ID: dsh-proxy-control@eb84c3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
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: github · https://github.com/Joker-Principal/dsh-proxy-control (version unstated)
ID: dsh-proxy-control@eb84c3@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/Joker-Principal/dsh-proxy-control (version unstated)
ID: dsh-proxy-control@eb84c3@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/Joker-Principal/dsh-proxy-control (version unstated)
ID: dsh-proxy-control@eb84c3@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Joker-Principal/dsh-proxy-control (version unstated)
ID: dsh-proxy-control@eb84c3@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
164a29github✓ 1 runtime-verified2026-11-17
https://github.com/Joker-Principal/dsh-proxy-control
✓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/Joker-Principal/dsh-proxy-control#164a2984c4cf4b805c3a2ed89fc6c86ac4e86567
ID: dsh-proxy-control@164a2984c4cf4b805c3a2ed89fc6c86ac4e86567@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-17 · expires: 2026-11-24
View checks & evidence
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
↳ carried from earlier record dsh-proxy-control@eb84c3@dsh0.2.2-rc.3 (l4-sandbox)
active in loader tree (206 entries)
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-proxy-control/?ref=badge)``[](https://www.dsh.so/artifact/dsh-proxy-control/?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 low (authoritative when present) → overall low.
v0.7.9dsh manifest0.7.9git2026-11-180.7.9same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningnetIp · network
client/client.js:52'例如 http://127.0.0.1:7890。SOCKS 暂不支持:Harness 的联网抓取(web_fetch)只能经由 http/https 代理,SOCKS 覆盖不到它。', - warningnetIp · network
client/client.js:106'For example http://127.0.0.1:7890. SOCKS is not supported yet: the Harness web fetch can only go through an http/https proxy, so SOCKS cann - warningnetIp · network
client/client.js:637placeholder: 'http://127.0.0.1:7890', - warningnetIp · network
lib/index.js:92proxy: z.string().default("").description("手动模式下的代理地址,例如 http://127.0.0.1:7890。只接受 http:// 与 https://。").volatile(), - warningnetIp · network
lib/logic.js:20export const PROXY_PLACEHOLDER = "http://127.0.0.1:7890"; - warningnetIp · network
lib/logic.js:35return { ok: false, reason: "不是合法的 URL(要带协议,例如 http://127.0.0.1:7890)" }; - warningshellExec · shell
lib/system-proxy.js:43execFile("reg.exe", args, { timeout: timeoutMs, windowsHide: true, encoding: "utf8" }, (error, stdout) => {
show 2 audit findings
- lowSelf-test route performs a server-side fetch of a caller-supplied URL
lib/index.js:554The /proxy-control/test handler passes body.testUrl straight into probe(), so the Node process will fetch arbitrary http(s) targets (including intranet hosts reachable from the host). Impact is limited: the request only comes back as status/latency text, the route requires a loopback peer, a loopback Host header and a JSON content-type, and any caller able to reach it can already point the proxy anywhere.
- lowProxy URLs with embedded credentials are accepted, stored in cleartext and logged
lib/logic.js:42inspectProxyUrl detects userinfo but the flag is never used, so 'http://user:pass@host:port' is saved verbatim into cordis.patch.yml and published via the environment snapshot; the resolved proxy string is also written to the plugin log (lib/index.js: "出站请求经由 %s"), so proxy credentials can end up in config files and logs in plaintext.
Local-only proxy settings plugin with solid route guards; only two low-risk notes (self-test SSRF surface, cleartext proxy credentials). Static 'warn' flags are contextually safe.
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-04 · activity: Stable
• Repo created: 2026-10-04
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 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 @Joker-Principal/dsh-proxy-control?
@Joker-Principal/dsh-proxy-control 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 @Joker-Principal/dsh-proxy-control?
Run dsh plugin --profile web add github:Joker-Principal/dsh-proxy-control 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-18 (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.
