Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
What it doesAI
DSH left-column sidebar suite bundling a file tree, file opener, tools tab, LAN services panel, and long-running task tracker.
- File tree navigation and quick file opening in the DSH sidebar
- Tools tab with a LAN services panel for local network services
- Tracks long-running tasks from a single left-column view
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:Ln1m/dsh-side-suite#v0.1.3Install method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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 |
|---|---|---|---|
| v0.1.3 | ○ | ○ | ○ |
v0.1.3github○ 3 ecosystem plugin2026-10-19
https://github.com/Ln1m/dsh-side-suite
○dsh 0.2.1-rc.2current2026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Ln1m/dsh-side-suite#v0.1.3
ID: dsh-side-suite@v0.1.3@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
not present in web-profile loader inventory
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-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/Ln1m/dsh-side-suite#v0.1.3
ID: dsh-side-suite@v0.1.3@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
not present in web-profile loader inventory
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-14Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/Ln1m/dsh-side-suite#v0.1.3
ID: dsh-side-suite@v0.1.3@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
View checks & evidence
not present in web-profile loader inventory
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-side-suite/)`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 medium — stricter wins → overall medium.
—v0.1.3git2026-10-21v0.1.3same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningshellExec · shell
dsh-extensions-panel/lib/index.js:33execFile(file, args, { timeout: timeoutMs || 10000, windowsHide: true }, (err, stdout) => { - warningchildProcess · code-exec
dsh-lan-services/lib/index.js:85const child = spawn("powershell.exe", ["-NoProfile", "-NonInteractive", "-ExecutionPolicy", "Bypass", "-Command", script], { - warningchildProcess · code-exec
dsh-lan-services/lib/index.js:247const child = spawn(process.execPath, [script, String(p)], { detached: true, stdio: "ignore", windowsHide: true }); - warningfsWrite · files
dsh-lan-services/lib/index.js:164fs.writeFileSync(DATA_FILE, JSON.stringify(obj, null, 2), "utf8"); - warningfsWrite · files
dsh-lan-services/servers/static-server.cjs:42fs.appendFileSync(LOG_FILE, new Date().toISOString() + ' ' + msg + '\n'); - warningchildProcessImport · code-exec
dsh-lt-tasks/lib/readonly.js:1import { execFile } from "node:child_process";
show 5 audit findings
- mediumModel tools and task store are imported at runtime but absent from the audited source
dsh-lt-tasks/lib/index.js:1apply() registers every object in `tools` via ctx.tools.register(t), so model-callable tools run code that was never reviewed; store.js implements every filesystem operation behind the /lt-tasks routes and is likewise missing, as are the dsh-files-tree / dsh-files-open browser bundles. The audit cannot certify what actually executes in the host.
- mediumTask doc/delete routes pass raw client-supplied id/doc into the store without containment checks
dsh-lt-tasks/lib/routes.js:82The only validation is `typeof body?.id !== "string"`; body.id and body.doc are then handed to store.writeDoc, and body.id to store.deleteTask (line 103) and lock.release. If store builds paths with join(root, id, ...) without a path.relative guard (store.js is not in the dump), an id such as "../../.." yields arbitrary file write/delete with the DSH user's rights. Any client that can reach the DSH web server, including LAN clients if the UI is proxied, can send these POSTs.
- lowGlobal uncaughtException/unhandledRejection handlers installed in the DSH host process
dsh-lan-services/lib/index.js:34These run at module import time and change behaviour for the whole host: every unhandled error from any plugin is swallowed and the process is kept alive in a potentially inconsistent state, and real crashes are hidden from the user.
- lowPersisted script path is re-executed with node without integrity or origin check
dsh-lan-services/lib/index.js:247`script` is derived by scriptFromCmd from the command line of whatever process listens on 3090-3099, and then persisted in ~/.dsh/dsh-lan-services.json. Any local process, or any write to that JSON, can pin an arbitrary .js path that the panel later executes with node on a "start" click; the path is not confined to a services directory and is not re-verified against the original file.
- lowDisplay-mode change performed by an unauthenticated GET request
dsh-extensions-panel/lib/index.js:82A state-changing action (DisplaySwitch.exe) is reachable through GET /extensions/api/vdd?mode=on|off with no origin/token check or confirmation, so any web page the user visits can flip the desktop to extended mode and spawn two PowerShell processes per hit. Impact is disruption only — responses are not readable cross-origin.
Capabilities match the documented purpose and shell calls use fixed binaries or numeric-only args, but task ids reach an unreviewed store.js and tools.js is loaded without being audited.
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-08 · activity: Active
• Repo created: 2026-09-26
• Stars: ★ 2 · Forks: 1
• Health: Active — committed within last 30 days
Source
GitHub: github.com/Ln1m/dsh-side-suite
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).