Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
一个Deepseek Harness 的进程结束插件,在左下角会有关闭按钮,本插件还同时有页面切换,在应用模式时关闭进程会自动关闭当前页面,标签页模式则不行
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:SanYe-SanJiu/dsh-power-switch#v1.1.4Install 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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|
| v1.1.4 | ✓ | ✓ | ✓ |
v1.1.4github✓ 3 runtime-verified2026-10-19
https://github.com/SanYe-SanJiu/dsh-power-switch
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/SanYe-SanJiu/dsh-power-switch#v1.1.4
ID: dsh-power-switch@v1.1.4@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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.
✓dsh 0.2.1-alpha.42026-10-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/SanYe-SanJiu/dsh-power-switch#v1.1.4
ID: dsh-power-switch@v1.1.4@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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.
✓dsh 0.2.1-alpha.22026-10-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/SanYe-SanJiu/dsh-power-switch#v1.1.4
ID: dsh-power-switch@v1.1.4@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-15 · expires: 2026-10-22
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.
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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-power-switch/)``[](https://www.dsh.so/artifact/dsh-power-switch/)`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.
—v1.1.4git2026-10-21v1.1.4same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (12)
- warningnetIp · network
lib/host.js:609const target = appWindowTarget(new URL(request.url ?? '/', 'http://127.0.0.1').searchParams.get('next') ?? undefined) - warningchildProcess · code-exec
lib/index.js:612const outcome = spawnSync('cscript.exe', args, { stdio: 'ignore', windowsHide: true }) - warningchildProcess · code-exec
lib/index.js:952const child = spawn(process.execPath, [fileURLToPath(helper)], { - warningnetIp · network
lib/index.js:809const url = connectionCtx.connection.authenticatedUrl(`http://127.0.0.1:${String(port)}/`) - warningnetIp · network
lib/index.js:846writeRecordedTokenUrl(connectionCtx.connection.authenticatedUrl(`http://127.0.0.1:${String(port)}/`)) - warningnewFunction · code-exec
scripts/verify-client-artifact.mjs:107new Function('window', 'document', source)(windowStub, documentStub) - warningnetIp · network
scripts/verify-client-artifact.mjs:34const origin = `http://127.0.0.1:${String(port)}` - warningnetIp · network
scripts/verify-live.mjs:20const rawOrigin = process.argv[2] ?? 'http://127.0.0.1:3080' - warningnetIp · network
src/host.js:609const target = appWindowTarget(new URL(request.url ?? '/', 'http://127.0.0.1').searchParams.get('next') ?? undefined) - warningchildProcess · code-exec
src/index.js:612const outcome = spawnSync('cscript.exe', args, { stdio: 'ignore', windowsHide: true }) - warningchildProcess · code-exec
src/index.js:952const child = spawn(process.execPath, [fileURLToPath(helper)], { - warningnetIp · network
src/index.js:809const url = connectionCtx.connection.authenticatedUrl(`http://127.0.0.1:${String(port)}/`)
show 1 audit findings
- lowTrust fence relies only on Origin==Host, which a DNS-rebinding page can also satisfy
lib/host.js:95isTrustedRequest accepts any request whose Origin authority equals its Host. A page served from an attacker domain that re-resolves to 127.0.0.1 presents Origin and Host of that same authority, so it would pass the fence and could reach the state-changing routes (shutdown, restart, settings, shortcut). Real impact depends on the host's own session/token layer: the DSH cookie is scoped to 127.0.0.1 and is not sent to the rebound host, and the code comment states the Web host authenticates every request, so this is a defense-in-depth gap rather than a demonstrated exploit.
Loopback-only, Origin-checked routes for shutdown/restart/settings/shortcut; guards in lib/host.js verified, no reachable high-risk path in the harvested host code.
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-21 · activity: Active
• Repo created: 2026-09-22
• 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).
