Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
DSH plugin: route only the model channels you tick through an HTTP proxy, everything else stays direct — with a settings card in the Web UI.
Installation
dsh plugin --profile web add github:lilith1257/dsh-proxy-whitelistInstall method: GitHub · runtime verified (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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.1-rc.2 current |
|---|---|
| d99ba0 | ✓ |
d99ba0github✓ 1 runtime-verified2026-10-18
https://github.com/lilith1257/dsh-proxy-whitelist
✓dsh 0.2.1-rc.2current2026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/lilith1257/dsh-proxy-whitelist (version unstated)
ID: dsh-proxy-whitelist@d99ba0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-proxy-whitelist/)``[](https://www.dsh.so/artifact/dsh-proxy-whitelist/)`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 — stricter wins → overall low.
v0.6.3dsh manifest0.6.3git2026-10-210.6.3same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningnetIp · network
lib/client.js:182proxyHint: '本地代理客户端的 HTTP 端口,例如 http://127.0.0.1:7890。只支持 http:// 与 https://;SOCKS 会被说明并忽略。', - warningnetIp · network
lib/client.js:183proxyPath: '代理地址只能写到端口:不能带路径、问号参数或 # 片段。写成 http://127.0.0.1:7890 这样。', - warningnetIp · network
lib/client.js:246proxyHint: 'The HTTP port of your local proxy client, e.g. http://127.0.0.1:7890. Only http:// and https:// proxies are supported; a SOCKS U - warningnetIp · network
lib/index.js:56.default('http://127.0.0.1:7890') - warningnetIp · network
lib/index.js:58'HTTP proxy endpoint, e.g. http://127.0.0.1:7890. Only http:// and https:// proxies are supported; a SOCKS URL is reported and ignored. The
show 1 audit findings
- lowFallback loads undici by filesystem path instead of the module resolver
lib/router.js:376When `import('undici')` fails with ERR_MODULE_NOT_FOUND, the plugin imports and executes `<searchPath>/undici/index.js` from Node's standard resolution directories of the plugin and of `process.argv[1]`. Any pre-existing package planted in one of those node_modules directories would be executed with host privileges. Reachability requires a broken dependency install plus a planted package already on the harness resolution path, so this adds no capability beyond Node's own resolution and is a hardening gap, not a demonstrated attack path. The plugin never writes these paths and no attacker-contr
Well-scoped proxy-routing plugin: loopback-gated bridge, redacted credentials, no shell/eval; only a low-severity filesystem module-resolution fallback for undici.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-18 · activity: Active
• Repo created: 2026-10-18
• Stars: ★ 0 · 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).
