dsh-codex-ui avatar

dsh-codex-ui

DSH Codex UI — 为 DeepSeek Harness Web 提供 Codex 风格侧栏、工作区会话树、全局搜索和轮次导航 · A Codex-style sidebar, workspace session tree, global search, and turn navigation for DSH Web

PluginInterface & LayoutDesktopKnowledgeStorageFileWeb search
Verification
L5 · Run tested
stale
Risk
Medium
Health
Active
Trust
Silver

Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →

Install verification badge dsh 0.2.1-rc.2Install verification badge dsh 0.2.0-rc.2Install verification badge dsh 0.2.0-rc.1Install verification badge dsh 0.1.7-rc.2Install verification badge dsh 0.1.7-rc.1

Data as of (UTC)

What it doesAI

A DeepSeek Harness web plugin that restyles the UI with a Codex-like sidebar, workspace tree, search, and turn navigation.

  • Codex-style sidebar layout
  • Workspace tree integration
  • Search and turn navigation UI
interfaceAIfileAI

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 @michengai/dsh-codex-ui
verified

Install method: npm · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5

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, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.

GitHub stars
299★

current (registry 2026-11-17) · 8 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series

09-18 → 11-16 · 8 points

Weekly star gain
+19★

Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend

10-01 → 11-16 · 7 points

Cumulative downloads
406k

Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)

09-12 → 11-15 · 58 points

Weekly downloads
29k

Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count

09-12 → 11-16 · 59 points

npm snapshots 80 · 59 observed days · mirror included from 2026-10-18weekly board #30total board #12downloads ≠ unique usersstar weekly #79

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 · peerDependenciesdeclared in 1.1.37
supports any of: dsh 0.1.2-rc.1 or dsh 0.1.5-rc.1 or dsh 0.1.5-rc.2 or dsh 0.1.5-rc.3 or dsh 0.1.7-rc.1 or dsh 0.1.7-rc.2 or dsh 0.2.0-rc.1 or dsh 0.2.0-rc.2 or dsh 0.2.1-alpha.2

Based on 1 requirement(s) across 11 @deepseek-ai/dsh-* packages.

raw ranges0.1.2-rc.1 || 0.1.5-rc.1 || 0.1.5-rc.2 || 0.1.5-rc.3 || 0.1.7-rc.1 || 0.1.7-rc.2 || 0.2.0-rc.1 || 0.2.0-rc.2 || 0.2.1-alpha.2 ×11

✗ Running dsh 0.2.2-rc.3 is outside the declared range — the official install gate rejects it (incompatible-version).

To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-codex-ui@1.1.37 0.2.2-rc.3 (the exemption lives in the local profile; this site does not assume one)

Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).

Whether it actually runs is a separate question → see the measured matrix below (L1–L5).

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.2.1-rc.5dsh 0.2.1-rc.3dsh 0.2.1-rc.2dsh 0.2.1-alpha.4dsh 0.2.1-alpha.2
2.2.3·····
2.2.1·····
2.1.1·····
2.0.22·····
2.0.20·····
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
2.2.3npm2026-11-15

@michengai/dsh-codex-ui

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

2.2.1npm2026-11-14

@michengai/dsh-codex-ui

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

2.1.1npm2026-11-13

@michengai/dsh-codex-ui

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

2.0.22npm2026-11-12

@michengai/dsh-codex-ui

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

2.0.20npm2026-11-10

@michengai/dsh-codex-ui

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

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:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-codex-ui.svg)](https://www.dsh.so/artifact/dsh-codex-ui/?ref=badge)`
dsh 0.2.1-rc.2 install verified
`[![dsh.so install · dsh 0.2.1-rc.2](https://cdn.dsh.so/badge/install/dsh-codex-ui@0.2.1-rc.2.svg)](https://www.dsh.so/artifact/dsh-codex-ui/?ref=badge-install)`
dsh 0.2.0-rc.2 install verified
`[![dsh.so install · dsh 0.2.0-rc.2](https://cdn.dsh.so/badge/install/dsh-codex-ui@0.2.0-rc.2.svg)](https://www.dsh.so/artifact/dsh-codex-ui/?ref=badge-install)`
dsh 0.2.0-rc.1 install verified
`[![dsh.so install · dsh 0.2.0-rc.1](https://cdn.dsh.so/badge/install/dsh-codex-ui@0.2.0-rc.1.svg)](https://www.dsh.so/artifact/dsh-codex-ui/?ref=badge-install)`
dsh 0.1.7-rc.2 install verified
`[![dsh.so install · dsh 0.1.7-rc.2](https://cdn.dsh.so/badge/install/dsh-codex-ui@0.1.7-rc.2.svg)](https://www.dsh.so/artifact/dsh-codex-ui/?ref=badge-install)`
dsh 0.1.7-rc.1 install verified
`[![dsh.so install · dsh 0.1.7-rc.1](https://cdn.dsh.so/badge/install/dsh-codex-ui@0.1.7-rc.1.svg)](https://www.dsh.so/artifact/dsh-codex-ui/?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.

dsh-codex-uiAutomated review · daily

Static low; dynamic medium (authoritative when present) → overall medium.

static low→dynamic medium→overall medium
dynamic findings0 critical·0 high·1 medium·3 low
mediumoverall · medium
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv2.2.7dsh manifest
scanned version2.2.7npm2026-11-17
current version2.2.7same version
vet verdictclean · npm

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

show static findings (5)
  • warningchildProcess · code-execlib/desktop-menu-plugin.mjs:147

    return spawnSync(command, args, { encoding: 'utf8', timeout: 20000, windowsHide: true, env: childEnv })

  • warningchildProcess · code-execlib/desktop-menu-plugin.mjs:250

    const child = spawn(plan.appPath, [], {

  • warningchildProcess · code-execlib/desktop-menu-plugin.mjs:323

    const child = spawn(process.execPath, [scriptPath], {

  • warningfsWrite · fileslib/desktop-menu-plugin.mjs:119

    try { fs.appendFileSync(plan.logPath, '[' + stamp() + '] codex-ui restart: ' + message + '\\n') } catch {}

  • warningfsWrite · fileslib/desktop-menu-plugin.mjs:125

    fs.writeFileSync(plan.statePath, JSON.stringify({

2model reads redacted source context · never executes plugin code
highest grademedium
merged intooverall medium
audited at2026-11-11
audited artifactnpm 2.0.22

The artifact has changed (audited npm 2.0.22 → current npm 2.2.7): the conclusion is still counted conservatively and has been queued for re-audit; it is replaced once that audit lands.

findings0 critical·0 high1 medium / 3 low hidden
show 4 audit findings
  • mediumRestart token is issued by an unauthenticated status endpoint protected only by a forgeable Host headerlib/desktop-menu-plugin.mjs

    The only gate before ?action=status is hostIsLoopback(headerValue(request.headers, "host")), and the Host header is fully attacker-controlled outside browsers. Any caller that can reach the port (any local process, or a remote client if the DSH web server is ever exposed beyond loopback) can read the status document, obtain the per-boot restart token and the local appPath, then POST ?action=restart with x-dcu-restart-key to force-terminate (taskkill /F or SIGTERM) and relaunch the desktop app: a denial-of-service plus local path disclosure. Cross-site browser attacks are indeed blocked (no COR

  • lowComposer prediction endpoint fails open to 'owner' when the connection service is unavailablelib/composer-plugin.mjs

    The owner-only check is bypassed entirely if ctx.get('connection') is missing or throws (getService swallows exceptions and returns undefined). In that state any caller able to POST JSON with a live sessionId can drive model calls over that session's transcript and tool output. Reachability depends on a host configuration without the connection service, so this is a hardening gap rather than a demonstrated bypass.

  • lowRestart helper script is written to the shared temp directory under a timestamp-only name and then executedlib/desktop-menu-plugin.mjs

    os.tmpdir() is world-writable on Linux/macOS. The name is derived only from Date.now(), so another local user who wins the race can pre-create a symlink at the guessed path (writeFileSync follows symlinks, clobbering a file owned by the victim) or replace the file between writeFileSync and spawn, which runs it with the victim's node/Electron and the plugin's full environment. Exploitation needs a local co-resident attacker plus a timing race, so impact is limited but non-zero.

  • lowPrediction prompts ship conversation tail and tool results to the model providerlib/composer-plugin.mjs

    buildPrompt includes up to 500 chars of each tool-result body (file contents, command output) plus the last messages, and predict() sends that to llm.prepareCall with purpose 'composer-prediction' on the session's own route. Users enabling inline suggestions therefore transmit tool output to the provider for a purpose beyond the conversation itself; bounds (maxChars 8k, maxMessages 10, maxToolNotes 6) limit, but do not remove, the exposure. It goes to the provider already configured for the session, so the incremental leak is bounded.

Restart and prediction endpoints are largely well-guarded, but the restart token is handed out by an unauthenticated status endpoint protected only by a forgeable Host header.

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

• Repo created: 2026-08-14

• Stars: ★ 299 · Forks: 24

• Health: Active — committed within last 30 days

Source

GitHub: github.com/MichengAI/dsh-codex-ui

Frequently asked questions

What is dsh-codex-ui?

dsh-codex-ui 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 dsh-codex-ui?

Run dsh plugin --profile web add @michengai/dsh-codex-ui in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run 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-17 (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.

Was this page helpful?