@ChenJun25/dsh-console-plugin

DSH console panel: scan a QR code and control your DSH desktop from your phone

PluginDeveloperDesktopVision / OCR

Verification

L5 · Run tested

Verified

Risk

Critical

Health

Active

Trust

Silver

Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked 10-21Install verification details →

What it does

DSH console panel: scan a QR code and control your DSH desktop from your phone

Installation

dsh plugin --profile web add dsh-console-plugin

verified 0.5.28

Install 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

Declared DSH compatibilityfrom package.json · peerDependencies

author declared no dsh version requirement

○ The author declares no dsh version requirement — install is not blocked by version.

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.2 current	dsh 0.2.1-alpha.2
0.5.28	✓	·
0.5.1	·	✓

Install compatibility (by plugin version, dsh versions within)

Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed

0.5.28npm✓ 1 runtime-verified2026-10-21

dsh-console-plugin

✓dsh 0.2.1-rc.2current2026-10-21L5 · runtime verified

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: npm · dsh-console-plugin@0.5.28

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Passed

Install + runtime smoke verified in the dsh sandbox — installs and runs

L5 · runtime verified · valid for dsh 0.2.1-rc.2

ID: dsh-console-plugin@0.5.28@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-21 · expires: 2026-10-28

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-21

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-21

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-21

spec dsh-console-plugin · channel npm package · outcome ran · exit 0

check took: 5.3s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-21

spec dsh-console-plugin · channel npm package · outcome ran · exit 0

check took: 5.3s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-21

spec dsh-console-plugin · channel npm package · outcome ran · exit 0

check took: 5.3s

L5 · Run tested✓ Passed

active in loader tree (150 entries)

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-21

spec dsh-console-plugin · install mode reused L4 scratch

check took: 104ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-21

ready line dsh web: http://127.0.0.1:61618/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-21

path / · HTTP 200 · took 104ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE✓ Passed

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-21

verdict active · entries 150

match: include:dsh-console · file:///E:/AgentsWs/dsh.so-runners/scratch/l3sandbox-HOByB4/home/profiles/web/node_modules/dsh-console-plugin/lib/index.js · phase active

phases: active 122 · null 28

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

0.5.1npm✓ 1 runtime-verified2026-10-14

dsh-console-plugin

✓dsh 0.2.1-alpha.22026-10-14L5 · runtime verified

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.2
• Plugin artifact: npm · dsh-console-plugin@0.5.1

Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)

L1 static

Passed

L2 static

Passed

L3 static

Passed

L4 sandbox

Passed

L5 runtime

Passed

Install + runtime smoke verified in the dsh sandbox — installs and runs

L5 · runtime verified · valid for dsh 0.2.1-alpha.2

ID: dsh-console-plugin@0.5.1@dsh0.2.1-alpha.2 · profile: l4-sandbox

Issued: 2026-10-14 · expires: 2026-10-21

View checks & evidence

L1 · Found✓ Passed

Defaulted from L3L1.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L2 · Structured✓ Passed

Defaulted from L3L2.0_DEFAULTED_FROM_L3✓ Passed

defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)

L3 · Install spec✓ Passed

Install command parsedL3.1_INSTALL_COMMAND_PARSED✓ Passed

Source: registry verification · Method: install spec parse · Captured 2026-10-21

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

Source: registry verification · Method: DSH version declaration · Captured 2026-10-21

L4 · Install tested✓ Passed

Install executed in confined sandboxL4.1_INSTALL_EXECUTED_CONFINED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-console-plugin · channel npm package · outcome ran · exit 0

check took: 7.6s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-console-plugin · channel npm package · outcome ran · exit 0

check took: 7.6s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-console-plugin · channel npm package · outcome ran · exit 0

check took: 7.6s

L5 · Run tested✓ Passed

active in loader tree (150 entries)

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-14

spec dsh-console-plugin · install mode reused L4 scratch

check took: 213ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

Source: DSH runtime · Method: web boot · Captured 2026-10-14

ready line dsh web: http://127.0.0.1:58975/?token=…

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

Source: DSH runtime · Method: HTTP request · Captured 2026-10-14

path / · HTTP 200 · took 213ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE✓ Passed

Source: DSH runtime · Method: plugin inventory query · Captured 2026-10-14

verdict active · entries 150

match: include:dsh-console · file:///E:/AgentsWs/dsh.so-runners/scratch/l3sandbox-n7tlr0/home/profiles/web/node_modules/dsh-console-plugin/lib/index.js · phase active

phases: active 122 · null 28

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:

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.

dsh-console-pluginAutomated review · daily

Static low, dynamic high — stricter wins → overall high.

static low→dynamic high→overall high

0 critical·0 high

highoverall · high

1static scan · vet primaryvet AST static analysis (npm artifact or git source)

Version binding

plugin versionv0.5.28dsh manifest

scanned version0.5.28npm2026-10-21

current version0.5.28same version

vet verdictclean · npm

Vet is an AST static scan (npm artifact or git source).

show static findings (12)

warningfsWrite · fileslib/cloud-link.mjs:161
fs.writeFileSync(storePath, JSON.stringify(data, null, 2), { mode: 0o600 })
warningfsWrite · fileslib/cloud-link.mjs:188
fs.writeFileSync(tunnelAutoPath, json, { mode: 0o600 })
warningchildProcess · code-execlib/dsh-console-cloud.mjs:229
child = spawn(cmd, args, { cwd: opts.cwd || undefined, env, windowsHide: true, stdio: ['ignore', 'pipe', 'pipe'] })
warningfsWrite · fileslib/dsh-console-cloud.mjs:465
fs.writeFileSync(f, JSON.stringify(entry, null, 2))
warningfsWrite · fileslib/frpc-bootstrap.mjs:105
fs.writeFileSync(tmp, buf, { mode: 0o755 })
warningfsWrite · fileslib/frpc-bootstrap.mjs:107
try { fs.chmodSync(target, 0o755) } catch (_) { }
warningfsWrite · fileslib/mp-support.mjs:79
fs.writeFileSync(tmp, JSON.stringify(data, null, 2))
warningfsWrite · fileslib/mp-support.mjs:146
fs.writeFileSync(tmp, JSON.stringify(data, null, 2))
warningchildProcess · code-execlib/tunnel.mjs:261
c = spawn(rt.frpcPath, ["-c", GEN_TOML_PATH], {
warningshellExec · shelllib/tunnel.mjs:201
execFile("powershell.exe", ["-NoProfile", "-NonInteractive", "-Command", cmd],
warningfsWrite · fileslib/tunnel.mjs:165
fs.writeFileSync(tomlPath, buf, { mode: 0o600 })
warningfsWrite · fileslib/wan-meter.mjs:65
fs.writeFileSync(file, JSON.stringify(data, null, 2), { mode: 0o600 })

2dynamic auditmodel reads redacted source context · never executes plugin code

highest gradehigh

merged intooverall high

audited at2026-10-17

findings0 critical·1 high1 medium / 1 low hidden

show 3 audit findings

highSession-delete op passes unvalidated sessionId into path.join + recursive fs.rmSynclib/index.js
sessionId is only String()-cast, never checked for path separators. A caller able to reach op=delete (LAN /dsh-console/cmd bridge with the access token or a paired-device cookie, or the panel /api/dsh-console/cmd route) can send a sessionId such as '../../../../../../Users/victim/Documents': path.join normalises it out of sessionsRoot, fs.statSync matches any existing directory, and fs.rmSync(recursive:true, force:true) deletes that directory tree. This escalates the intended 'delete my session' capability (already a significant capability for an authenticated phone client) into unrestricted r
mediumSilent auto-registration and 60s heartbeat of a persistent device id to a third-party cloud hostlib/cloud-link.mjs:9
gaoshou25.cn is not a DSH/official endpoint and there is no user-facing opt-in: every plugin load auto-POSTs to /register with a persistent nodeId (stored in ~/.dsh/dsh-console-cloud.json) plus platform, and thereafter heartbeats /status every 60s; bind()/applyNode() additionally upload the bound user's uid/name/avatar. This is an undisclosed outbound identity/telemetry channel from the user's machine to a third party, uncorrelated with the plugin's stated LAN/panel purpose.
lowCloud device credential nodeId generated with Math.random instead of a CSPRNGlib/cloud-link.mjs:31
The file's own comments state nodeId is '这台电脑在云端的身份凭据' and it is the only identifier accepted by /register, /bind, /redeem and /status. Math.random is not a CSPRNG (V8 xorshift128+, predictable/recoverable), so the credential is weaker than the 32-hex length suggests; guessing or state-recovery could let a third party impersonate this node against the cloud endpoints. No direct exploit path was demonstrated from this code alone.

Confirmed: sessionId is used unsanitised in an fs.rmSync path (arbitrary recursive directory deletion behind the LAN token), plus a silent third-party cloud beacon.

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-19 · activity: Active

• Repo created: 2026-10-18

• Stars: ★ 2 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/ChenJun25/dsh-console-plugin

Plugin notes

What is the @ChenJun25/dsh-console-plugin DeepSeek Harness plugin?

@ChenJun25/dsh-console-plugin is a DeepSeek Harness plugin maintained by @ChenJun25. It is cataloged on dsh.so as a Developer plugin for Vision / OCR tasks, with a public GitHub source, declared install command, and automated static scan results; plugins static-flagged at warn or above also carry a model-driven dynamic security audit record.

How do I install @ChenJun25/dsh-console-plugin?

Run dsh plugin --profile web add dsh-console-plugin in a DeepSeek Harness (dsh) environment. This exact command has been verified by a real install inside an isolated windows-acl sandbox (L4) plus web smoke testing (L5).

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 (it can produce false positives and miss context), and the dynamic security audit has a model read the harvested source context with secret files stripped and content redacted inline — plugin code is never executed. The dynamic audit only covers plugins static-flagged at warn or above, and its conclusion can only raise the combined verdict, never exempt it. Neither layer is a manual security audit or an endorsement; before using a plugin, review the repository and installed permissions, and combine both with the verification level (L4/L5) and health signals.

"DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI. It uses an architecture where everything is a plugin, and is powered by Cordis."
— DeepSeek Harness README

Sources: GitHub repository · DeepSeek Harness README · security scan data · Maintained by dsh.so · Last updated 2026-10-21

@ChenJun25/dsh-console-plugin

What it does

Installation

Verification & Compatibility

Author badges

Security Report

Activity

Source

Author README