Device-workspace federation plugin for the dsh web GUI: pair into another DSH instance and browse its projects and sessions from the local sidebar, with each peer session opening in the local center column through a loopback embed proxy.
Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Pairs with another DSH instance to browse its projects and sessions from the local sidebar, opening peer sessions in the center column via a loopback proxy.
- Pair with a remote DSH instance
- Browse remote projects and sessions from local sidebar
- Open peer sessions in local center column via loopback proxy
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.
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling (a rotating daily shard); the npm pair from every snapshot.
4 samples (roughly every 7 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
09-24 → 10-19 · 4 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-01 → 10-19 · 3 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:njjpro/dsh-remote-workspaceInstall method: GitHub · sandbox install ok, web smoke failed (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.2-rc.1 current | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| f7ceee | ✗ | ✗ | ✗ | ✗ | ✗ |
f7ceeegithub10 failed2026-11-05
https://github.com/njjpro/dsh-remote-workspace
✗dsh 0.2.2-rc.1current2026-11-05L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/njjpro/dsh-remote-workspace (version unstated)
ID: dsh-remote-workspace-6@f7ceee@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.52026-11-02L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/njjpro/dsh-remote-workspace (version unstated)
ID: dsh-remote-workspace-6@f7ceee@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-02 · expires: 2026-11-09
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.32026-10-27L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/njjpro/dsh-remote-workspace (version unstated)
ID: dsh-remote-workspace-6@f7ceee@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.1-rc.22026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/njjpro/dsh-remote-workspace (version unstated)
ID: dsh-remote-workspace-6@f7ceee@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/njjpro/dsh-remote-workspace (version unstated)
ID: dsh-remote-workspace-6@f7ceee@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
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-10L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/njjpro/dsh-remote-workspace (version unstated)
ID: dsh-remote-workspace-6@f7ceee@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.0-rc.22026-10-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/njjpro/dsh-remote-workspace (version unstated)
ID: dsh-remote-workspace-6@f7ceee@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.2.0-rc.12026-09-29L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/njjpro/dsh-remote-workspace (version unstated)
ID: dsh-remote-workspace-6@f7ceee@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗dsh 0.1.7-rc.22026-09-25L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/njjpro/dsh-remote-workspace (version unstated)
ID: dsh-remote-workspace-6@f7ceee@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-rc.12026-09-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/njjpro/dsh-remote-workspace (version unstated)
ID: dsh-remote-workspace-6@f7ceee@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
This level was not executed in this scan.
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/njjpro/dsh-remote-workspace (version unstated)
ID: dsh-remote-workspace-6@f7ceee@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-remote-workspace-6/?ref=badge)`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.3.18dsh manifest0.3.18git2026-11-050.3.18same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningnetIp · network
src/client/PeerSessionView.tsx:56new Image().src = `http://127.0.0.1:43121/assets/__probe_occl-${summary}_${Date.now()}.gif` - warningnetIp · network
src/client/peer-mount.tsx:56new Image().src = `http://127.0.0.1:43121/assets/__probe_${encodeURIComponent(tag)}_${Date.now()}.gif` - warningnetIp · network
src/client/peer-mount.tsx:92new Image().src = `http://127.0.0.1:43121/assets/__probe_classes-${encodeURIComponent(samples.join('|')).slice(0, 140)}_${now}.gif` - warningnetIp · network
src/client/peer-mount.tsx:107new Image().src = `http://127.0.0.1:43121/assets/__probe_centerchain-${encodeURIComponent(chain.join('>')).slice(0, 140)}_${now}.gif` - warningchildProcess · code-exec
src/index.ts:173spawn('rundll32', ['url.dll,FileProtocolHandler', url], { stdio: 'ignore', detached: true }).unref() - warningchildProcess · code-exec
src/index.ts:175spawn('open', [url], { stdio: 'ignore', detached: true }).unref() - warningchildProcess · code-exec
src/index.ts:177spawn('xdg-open', [url], { stdio: 'ignore', detached: true }).unref()
show 4 audit findings
- mediumDiagnostic beacons send document/DOM structure to a fixed loopback port, including while the plugin gate is closed
src/client/peer-mount.tsx:56runFace's 300 ms keep-alive loop emits beacons on every gate/host transition, and the probing continues down the 'gate-closed' branch (line 62) when the feature switch is OFF. The harder-coded port 43121 is not read from the peerEmbedPort config, and it is only bound by this plugin's own proxy when the plugin is enabled and peerBaseUrl is set; otherwise whatever local process listens on that port receives the payload. The payload includes real shell reconnaissance: sampled class names of every element matching sidebar|center|col|list|frame|main|content (line ~91), the element chain at the wind
- medium'Open in browser' passes an unvalidated URL straight to OS protocol handlers (rundll32/open/xdg-open)
src/index.ts:177The openExternal callback registered into makePeerControlRoutes (line 168) forwards `url` verbatim to `rundll32 url.dll,FileProtocolHandler` on Windows (line 173), `open` on macOS (line 175) and `xdg-open` on Linux. Spawn with an argv array prevents shell metacharacter injection, but there is no scheme/host allow-list: a file://, smb:// or custom-scheme URL, or a path to a local .exe/.app/.desktop, is handed to the OS handler, which on Windows and macOS can launch a local program. The URL is peer-derived (it comes from the paired peer's session data via /api/pair/peer/*), so a paired-but-hosti
- lowUnbounded synchronous append to a boot-probe log on the request path
src/index.ts:140Every probe line the embed proxy forwards is appended synchronously to a file in DSH_HOME with no size cap, rotation or newline sanitisation. A busy or hostile peer driving proxy traffic can grow the file without limit (disk exhaustion) and, if `line` embeds attacker-influenced text containing newlines, forge log entries. The content of `line` is produced in the un-harvested src/peer-proxy.ts, so the injection part is unconfirmed; the unbounded sync growth is visible here.
- lowPeer session iframes load a peer-supplied URL with no sandbox or permission restrictions
src/client/PeerSessionView.tsx:153The iframe is created with only className/src/title/data-* attributes: no `sandbox` and no `allow` restrictions. The URL is the ticket URL returned by /api/pair/peer/embed-ticket, i.e. content ultimately controlled by the paired peer. Cross-origin isolation still applies (the proxy serves from a different port than the local shell), so this is not a same-origin bypass, but the embedded document retains default powers such as top-level navigation and downloads, and it also receives the focus grants performed by grantFrameFocus in this component.
Diagnostic beacons spray DOM structure to a fixed loopback port and an unvalidated URL is handed to OS protocol handlers; host route/proxy sources were not harvested.
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-09-23 · activity: Stable
• Repo created: 2026-09-22
• Stars: ★ 1 · Forks: 0
• Health: Stable — committed within 90 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).
Frequently asked questions
What is @njjpro/dsh-remote-workspace?
@njjpro/dsh-remote-workspace is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
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 @njjpro/dsh-remote-workspace?
Run dsh plugin --profile web add github:njjpro/dsh-remote-workspace in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed yet.
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-11-05 (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.