@DuJunxi1993/DSH-Shell

Native desktop shells for the DeepSeek Harness (dsh) web UI: a Tauri app for Windows and a SwiftUI app for macOS, one per top-level directory.

Ecosystem pluginDesktopDeveloperBrowserTerminalWeb searchTerminal / Shell

Verification

L5 · Ecosystem plugin

Ecosystem plugin

Risk

LowRisk

Health

Active

Trust

Silver

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

Native desktop shells for the DeepSeek Harness web UI, with a Tauri app for Windows and a SwiftUI app for macOS.

Tauri-based Windows shell built on WebView2
SwiftUI macOS shell built on WKWebView
One app per top-level directory, separate Rust and Swift codebases

desktopAI

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:DuJunxi1993/DSH-Shell#windows-v0.2.0

verified windows-v0.2.0

Install 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

Declared DSH compatibilityfrom package.json · peerDependencies

package manifest not collected

package manifest not collected — the declared range is unknown.

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

○ Ecosystem plugin

At-a-glance → evidence in the cards below

plugin ＼ dsh	dsh 0.2.1-rc.2 current	dsh 0.2.1-alpha.4	dsh 0.2.1-alpha.2
windows-v0.2.0	○	○	✗

Install compatibility (by plugin version, dsh versions within)

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

windows-v0.2.0github○ 2 ecosystem plugin1 failed2026-10-19

https://github.com/DuJunxi1993/DSH-Shell

○dsh 0.2.1-rc.2current2026-10-19Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-rc.2
• Plugin artifact: github · https://github.com/DuJunxi1993/DSH-Shell#windows-v0.2.0

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

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: dsh-shell-6@windows-v0.2.0@dsh0.2.1-rc.2 · profile: l4-sandbox

Issued: 2026-10-19 · expires: 2026-10-26

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-18

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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-19

spec github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · channel GitHub source · outcome ran · exit 0

check took: 2.0s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · channel GitHub source · outcome ran · exit 0

check took: 2.0s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · channel GitHub source · outcome ran · exit 0

check took: 2.0s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

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

spec github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · install mode reused L4 scratch

check took: 2.9s

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

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

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

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

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

path / · HTTP 200 · took 2.9s

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

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

verdict not-found · entries 149

phases: active 121 · null 28

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-17Ecosystem plugin

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.4
• Plugin artifact: github · https://github.com/DuJunxi1993/DSH-Shell#windows-v0.2.0

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

Unknown

Ecosystem plugin: no install verdict — not a usable dsh plugin (shown as L5 · ecosystem plugin)

Ecosystem plugin

ID: dsh-shell-6@windows-v0.2.0@dsh0.2.1-alpha.4 · profile: l4-sandbox

Issued: 2026-10-17 · expires: 2026-10-24

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-18

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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-17

spec github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · channel GitHub source · outcome ran · exit 0

check took: 2.9s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · channel GitHub source · outcome ran · exit 0

check took: 2.9s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · channel GitHub source · outcome ran · exit 0

check took: 2.9s

L5 · Run tested? Unknown

not present in web-profile loader inventory

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

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

spec github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · install mode reused L4 scratch

check took: 228ms

Web boot readyL5.2_WEB_BOOT_READY✓ Passed

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

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

HTTP endpoint servedL5.3_HTTP_SERVED✓ Passed

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

path / · HTTP 200 · took 228ms

Plugin active in inventoryL5.4_PLUGIN_INVENTORY_ACTIVE? Unknown

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

verdict not-found · entries 149

phases: active 121 · null 28

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 · L5 · failed

Environment & artifact

• Node.js: v24.14.0
• DSH: 0.2.1-alpha.2
• Plugin artifact: github · https://github.com/DuJunxi1993/DSH-Shell#windows-v0.2.0

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

Failed

Sandbox install failed

Ecosystem plugin · L5 · failed

ID: dsh-shell-6@windows-v0.2.0@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-18

DSH version declaredL3.2_DSH_VERSION_DECLARED✓ Passed

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

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 github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · channel GitHub source · outcome ran · exit 0

check took: 5.4s

Install succeededL4.2_INSTALL_SUCCESS✓ Passed

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

spec github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · channel GitHub source · outcome ran · exit 0

check took: 5.4s

Installed artifact confirmedL4.3_ARTIFACT_CONFIRMED✓ Passed

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

spec github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · channel GitHub source · outcome ran · exit 0

check took: 5.4s

L5 · Run tested✕ Failed

Sandbox install passedL5.1_INSTALL_PASSED_SANDBOXED✓ Passed

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

spec github:DuJunxi1993/DSH-Shell#windows-v0.2.0 · install mode reused L4 scratch

check took: 0ms

Web boot readyL5.2_WEB_BOOT_READY✕ Failed

boot failed

HTTP endpoint servedL5.3_HTTP_SERVED✕ Failed

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:

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-shell-6Automated review · daily

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

static low→dynamic medium→overall medium

0 critical·0 high

mediumoverall · medium

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

Version binding

plugin version—

scanned versionwindows-v0.2.0git2026-10-21

current versionwindows-v0.2.0same version

vet verdictclean · git

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

show static findings (6)

warningnetIp · networkwindows/src-tauri/src/endpoint.rs:10
//! dsh web: http://127.0.0.1:3080/?token=<launchToken>
warningnetIp · networkwindows/src-tauri/src/endpoint.rs:18
//! http://127.0.0.1:18787` is dsh's internal HTTP proxy. An earlier version
warningnetIp · networkwindows/src-tauri/src/endpoint.rs:250
let url = endpoint_from_line("dsh web: http://127.0.0.1:3080/?token=abc123", PORT)
warningnetIp · networkwindows/src-tauri/src/navigate.rs:27
// Compared as origins, not as string prefixes: `http://127.0.0.1:1` must not
warningnetIp · networkwindows/src-tauri/src/navigate.rs:28
// match `http://127.0.0.1:12`, and a path or query on the dsh origin is
warningnetIp · networkwindows/src-tauri/src/navigate.rs:51
const DSH: &str = "http://127.0.0.1:3080";

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

highest grademedium

merged intooverall medium

audited at2026-10-19

findings0 critical·0 high1 medium / 2 low hidden

show 3 audit findings

mediumdsh launch token is written verbatim to logs and into error tailswindows/src-tauri/src/endpoint.rs:136
Every stdout line of dsh is logged unredacted, and the only line that matters is `dsh web: http://127.0.0.1:3080/?token=<launchToken>`; the same line is also pushed into OutputTail and embedded into DshExitedBeforeReady/EndpointTimeout messages that are logged or shown to the user. Anyone able to read the log (bug reports, support bundles, other processes under the same account) obtains an authenticated URL to the running harness, which can drive the agent for the lifetime of that dsh process.
lowPID-scoped tree kill can run after the child has been reaped and its PID recycledwindows/src-tauri/src/platform.rs:101
shutdown() is documented idempotent and is followed by Drop, but both kill by the stored PID without first checking `is_dead(child)`. After the first shutdown has waited on (reaped) the child, `self.pid` is still Some, so a later shutdown/Drop signals a PID that the OS may have handed to an unrelated process (killpg on Unix, taskkill /T /F on Windows). The file's own claim that a PID-scoped kill 'can only ever reach the subtree under a PID we captured' does not hold once that PID is released.
lowApp-origin check accepts any tauri:// host and any scheme on tauri.localhostwindows/src-tauri/src/navigate.rs:38
The doc comment says this exists to allow 'the app's own origin, which serves the boot placeholder', but the predicate ignores the host for `tauri://` and ignores the scheme/port for `tauri.localhost`. A document reached as `https://tauri.localhost/...` (or `tauri://anything`) is therefore treated as internal and allowed to load inside the shell; if name resolution for tauri.localhost were ever influenced, remote content would render in the trusted shell, which also carries the injected native bridge wherever init scripts apply.

No critical or high risk: the shell validates the loopback+token endpoint, restricts navigation and kills only its own process tree, but writes the dsh launch token into logs.

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

• Repo created: 2026-08-14

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/DuJunxi1993/DSH-Shell

Plugin notes

What is @DuJunxi1993/DSH-Shell?

@DuJunxi1993/DSH-Shell is an ecosystem plugin maintained by @DuJunxi1993: it installs via dsh plugin add but declares no dsh.bundle and mounts nothing — installing it adds no plugin capability; use the source repository directly. It is cataloged on dsh.so as a Desktop entry, with a public source repository and automated static security scan.

How do I install @DuJunxi1993/DSH-Shell?

This is an ecosystem plugin: it installs via dsh plugin add but declares no dsh.bundle and mounts nothing — installing one adds no plugin capability; use the source repository directly. Its level reads L5 · Ecosystem plugin; 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 (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-16

@DuJunxi1993/DSH-Shell

What it doesAI

Installation

Verification & Compatibility○ Ecosystem plugin

Author badges

Security Report

Activity

Source

Author README