Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
Windows DSH bundle: route the pwsh tool to PowerShell 7, with per-user detection/install and sandbox-aware execution.
Installation
dsh plugin --profile web add dsh-plugin-pwsh7Install method: npm · 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 | dsh 0.2.1-alpha.4 |
|---|---|---|
| 0.3.3 | · | · |
| 0.1.1 | ✓ | · |
| v0.1.1 | · | · |
| 0.1.0 | · | ✓ |
0.3.3npm2026-10-21
dsh-plugin-pwsh7
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.1.1npm✓ 1 runtime-verified2026-10-19
dsh-plugin-pwsh7
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-plugin-pwsh7@0.1.1
ID: dsh-plugin-pwsh7@0.1.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-plugin-pwsh7@0.3.3@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-plugin-pwsh7@0.3.3@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-plugin-pwsh7@0.3.3@dsh0.2.1-rc.2 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.1github2026-10-18
https://github.com/drliuhuan/dsh-plugin-pwsh7
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.1.0npm✓ 1 runtime-verified2026-10-18
dsh-plugin-pwsh7
✓dsh 0.2.1-alpha.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-plugin-pwsh7@0.1.0
ID: dsh-plugin-pwsh7@0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-plugin-pwsh7@0.3.3@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-plugin-pwsh7@0.3.3@dsh0.2.1-rc.2 (l3-fullscan)
↳ carried from earlier record dsh-plugin-pwsh7@0.3.3@dsh0.2.1-rc.2 (l3-fullscan)
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-plugin-pwsh7/)``[](https://www.dsh.so/artifact/dsh-plugin-pwsh7/)`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.3.3dsh manifest0.3.3npm2026-10-210.3.3same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (3)
- warningshellExec · shell
lib/elevate.mjs:86execFile(file, args, options, (error, stdout, stderr) => { - warningfsWrite · files
lib/elevate.mjs:105fs.writeFileSync(scriptPath, elevatedPublishScript({ from, to, pathDir, logPath: markerPath }), 'utf8'); - warningfsWrite · files
lib/elevate.mjs:106fs.writeFileSync(wrapperPath, elevatedWrapperScript({ powershell, script: scriptPath, marker: markerPath }), 'utf8');
show 2 audit findings
- lowDownloaded PowerShell zip is extracted and its pwsh.exe executed without checksum or Authenticode verification
lib/install.mjsThe only integrity gate before executing the downloaded binary is a 5 MiB size floor and the 4-byte PK header. A TLS-intercepting proxy, a compromised CA, or a tampered redirect target could deliver any executable that would then be run as pwsh (and later on every `pwsh` tool call). No demonstrated impact without such a precondition.
- lowState-changing setup routes accept requests without an Origin header and have no authentication
lib/setup-routes.mjsBrowser cross-site POSTs are effectively blocked (JSON content-type + preflight), but any non-browser client that can reach the DSH web port can start a ~100 MB download, and on an elevated host request scope=system (machine PATH + Program Files writes) or cancel a running install. Impact needs the web server to be reachable beyond the local user, which is not demonstrated here.
Windows-only PowerShell 7 installer/router; no shell:true, no injection, fixed HTTPS source — only low hardening gaps (no binary integrity check, unauthenticated setup routes).
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: ★ 3 · 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).