This repository has been renamed: Ln1m/dsh-side-suite — click to visit the new location. Everything below is preserved as originally indexed.
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 →
Data as of (UTC)
What it doesAI
Left-column DSH suite that auto-detects local HTTP services on ports 3090-3099, shows LAN URLs, and starts/stops them with one click.
- Auto-detects local HTTP services on ports 3090-3099
- One-click start/stop; LAN URLs refresh when network changes
- Adds file tree, file opener, tools tab and long-task panel
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-lan-services#v0.1.3Install method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.0-rc.2
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.0-rc.2 | dsh 0.2.0-rc.1 | dsh 0.1.7-rc.2 | prehistory |
|---|---|---|---|---|
| v0.1.3 | ○ | · | · | · |
| v0.1.2 | · | · | · | ○ |
v0.1.3github○ 1 ecosystem plugin2026-10-08
https://github.com/Ln1m/dsh-lan-services
○dsh 0.2.0-rc.22026-10-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/Ln1m/dsh-lan-services#v0.1.3
ID: dsh-lan-services@v0.1.3@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
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.
v0.1.2github○ 1 ecosystem plugin2026-10-05
https://github.com/Ln1m/dsh-lan-services
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Ln1m/dsh-lan-services#v0.1.2
ID: dsh-lan-services@v0.1.2@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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.
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-lan-services/?ref=badge)``[](https://www.dsh.so/artifact/dsh-lan-services/?ref=badge-install)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
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 (authoritative when present) → overall medium.
—v0.1.2git2026-10-08v0.1.3version moved onclean · 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 2 audit findings
- mediumUnauthenticated /lan-services start/stop routes can spawn and kill local processes
dsh-lan-services/lib/index.js:241The plugin adds no session/CSRF check of its own; authorization depends entirely on the host webServer. Any client that can reach the DSH web server (for example a LAN device when the sibling wifi-access proxy is enabled) can POST to /lan-services/api/stop to kill whatever is listening on 3090-3099, or to /lan-services/api/start to relaunch a persisted node script. Ports are range-checked and scripts come only from locally observed command lines, so this is process-control/DoS rather than arbitrary code injection.
- lowStatic server binds 0.0.0.0 and /api/net discloses the absolute root path
dsh-lan-services/servers/static-server.cjs:144The server listens on 0.0.0.0 (listen call at the end of the file) with no authentication and, via /api/net, returns the absolute filesystem path of the served root to any LAN host. Serving the configured tree over the LAN is the intended feature, but the banner needlessly exposes local path structure and there is no access control if the root contains sensitive files.
No injection/RCE found; but start/stop HTTP routes lack auth and the static server binds 0.0.0.0, so a LAN-reachable DSH host exposes process control and file serving.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.
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: Stable
• Repo created: 2026-09-26
• Stars: ★ 2 · Forks: 1
• Health: Stable — committed within 90 days
Source
GitHub: github.com/Ln1m/dsh-lan-services
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
Frequently asked questions
What is @Ln1m/dsh-lan-services?
@Ln1m/dsh-lan-services is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install @Ln1m/dsh-lan-services?
Run dsh plugin --profile web add github:Ln1m/dsh-lan-services#v0.1.2 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
How does the security scan relate to a manual audit?
Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-10-19 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.