Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
DSH Desktop 右上角电源菜单:关闭 / 重启整个应用。Windows only, MIT.
Installation
dsh plugin --profile web add github:xichen-62/dsh-power-menuInstall 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 | dsh 0.2.1-alpha.4 |
|---|---|---|
| v0.1.17 | · | · |
v0.1.17github2026-10-21
https://github.com/xichen-62/dsh-power-menu
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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-power-menu/)``[](https://www.dsh.so/artifact/dsh-power-menu/)`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.1.17dsh manifestv0.1.17git2026-10-21v0.1.17same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningchildProcess · code-exec
lib/helper.cjs:240const child = spawn(copiedCmd, ['/d', '/c', 'exit', '0'], { - warningchildProcess · code-exec
lib/helper.cjs:298const child = spawn(shell, ['-NoProfile', '-NonInteractive', '-EncodedCommand', encoded], { - warningchildProcess · code-exec
lib/helper.cjs:444child = spawn(exe, [], { - warningshellExec · shell
lib/helper.cjs:89execFileSync('taskkill', ['/PID', String(pid), '/F'], { stdio: 'ignore', windowsHide: true }) - warningshellExec · shell
lib/helper.cjs:344const out = execFileSync(shell, ['-NoProfile', '-NonInteractive', '-Command', script], { - warningfsWrite · files
lib/helper.cjs:70fs.appendFileSync(LOG_PATH, `[${new Date().toISOString()}] ${line}\n`, 'utf8') - warningfsWrite · files
lib/helper.cjs:233fs.writeFileSync(jsonPath, JSON.stringify(payload), 'utf8') - warningchildProcess · code-exec
lib/index.js:162const helper = spawn(process.execPath, [HELPER, handoffPath], {
Destructive shutdown/restart routes are double-fenced (loopback socket + Host + Origin) and only act in the desktop build; taskkill/spawn use internally-derived PIDs and process.execPath, not request input.
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-20 · activity: Active
• Repo created: 2026-10-17
• Stars: ★ 12 · Forks: 2
• 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).
