Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
DSH plugin that runs the local Codex Computer Use runtime on Windows with native menu integration and auto-start.
- Runs the local Codex Computer Use runtime on Windows
- Native menu integration inside DSH
- Automatic startup of the runtime
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:Han-1413141/dsh-codex-computer-use#v0.1.4Install method: GitHub · 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.
6 samples (roughly every 7 days), 1 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
10-06 → 11-09 · 6 points
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-12 → 11-09 · 5 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
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
Only 0 points (< 3): no chart yet
no data yet
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
Based on 1 requirement(s) across 4 @deepseek-ai/dsh-* packages. raw ranges
0.2.0-rc.2 ×4
✗ 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-computer-use@0.1.4 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).
| plugin \ dsh | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| v0.1.4 | ✗ | ✗ | ✓ | ✓ | ✓ |
v0.1.4github✓ 4 runtime-verified2 failed2026-11-14
https://github.com/Han-1413141/dsh-codex-computer-use
✗dsh 0.2.1-rc.52026-11-01L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/Han-1413141/dsh-codex-computer-use#v0.1.4
ID: dsh-codex-computer-use@v0.1.4@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
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.
✗dsh 0.2.1-rc.32026-10-27L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Han-1413141/dsh-codex-computer-use#v0.1.4
ID: dsh-codex-computer-use@v0.1.4@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
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.
✓dsh 0.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Han-1413141/dsh-codex-computer-use#v0.1.4
ID: dsh-codex-computer-use@v0.1.4@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
active in loader tree (150 entries)
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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/Han-1413141/dsh-codex-computer-use#v0.1.4
ID: dsh-codex-computer-use@v0.1.4@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
active in loader tree (150 entries)
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/Han-1413141/dsh-codex-computer-use#v0.1.4
ID: dsh-codex-computer-use@v0.1.4@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Han-1413141/dsh-codex-computer-use#v0.1.4
ID: dsh-codex-computer-use@v0.1.4@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
↳ carried from earlier record dsh-codex-computer-use@v0.1.4@dsh0.2.2-rc.3 (l3-fullscan)
active in loader tree (150 entries)
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-codex-computer-use/?ref=badge)``[](https://www.dsh.so/artifact/dsh-codex-computer-use/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-codex-computer-use/?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.4dsh manifestv0.1.4git2026-11-16v0.1.4same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (4)
- warningnetIp · network
scripts/consent-ui-host.mjs:52DSH_PERMISSION_MODE: 'danger-full-access', DEEPSEEK_API_KEY: 'local-fixture', DEEPSEEK_BASE_URL: `http://127.0.0.1:${server.address().port}` - warningnetIp · network
scripts/menu-host.mjs:14DEEPSEEK_BASE_URL: 'http://127.0.0.1:9' }; - warningchildProcess · code-exec
src/client.mjs:15const child = fork(fileURLToPath(this.workerUrl), [], { stdio: ['ignore', 'ignore', 'ignore', 'ipc'], windowsHide: true, execArgv: [], env: - warningchildProcessImport · code-exec
src/windows-consent.mjs:1import { spawn } from 'node:child_process';
show 4 audit findings
- mediumForked computer-use worker inherits the full host environment, including model API keys
src/client.mjs:15Every computer-use call forks the worker with a copy of the entire host environment. That process loads the third-party @oai/sky runtime (package directory configurable through the plugin's `skyDir` option, see bin/cli.mjs) and may spawn codex.exe; all of them can read DEEPSEEK_API_KEY and any other credential exported in the DSH host process. No allow-list or stripping of secret variables is visible in the harvested code, and nothing indicates this exposure is disclosed to the user.
- lowConsent dialog executable path is resolved from the SystemRoot environment variable
src/windows-consent.mjs:9The PowerShell binary that renders the app-consent dialog is chosen from the inherited SystemRoot value rather than a fixed path. If the DSH process is launched with a poisoned environment (wrapper script, service/Task Scheduler env block, or malicious shortcut), the plugin would execute an arbitrary powershell.exe from that directory at consent time. The dialog payload itself is correctly passed as JSON on stdin, not interpolated into shell text.
- lowWorker installs a global nodeRepl shim that impersonates the Codex REPL to receive app-consent requests
src/approval.mjs:47To make @oai/sky route elicitation outside Codex, the worker replaces the process-global `nodeRepl` object with its own `createElicitation` implementation that forwards only computer-use app consent and declines everything else. The blast radius is limited: it refuses to overwrite an existing nodeRepl, is removed on dispose, and lives only in the forked worker process, so it does not affect the DSH host. Other code in that worker expecting the genuine Codex REPL object would see the shim.
- lowNative control bridge (src/runtime.mjs, src/controller.mjs, src/index.mjs, windows-consent.ps1) is referenced but absent from the audit set
src/worker.mjs:1The code that actually captures the screen, reads UI trees and injects mouse/keyboard input (controller.mjs, runtime.mjs) and the PowerShell dialog implementation (windows-consent.ps1, referenced at src/windows-consent.mjs:12) were not included in the harvested 15 files, even though package.json main is src/index.mjs. Those are exactly where a bypass of the consent gate, unsafe skyDir loading, or a dialog that accepts on close would live; they could not be verified here.
No backdoor or injection; consent gating fails closed, but the forked worker inherits the whole host environment (API keys) and the native control core was not in the audit set.
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-02 · activity: Stable
• Repo created: 2026-10-01
• Stars: ★ 1 · Forks: 1
• 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 @Han-1413141/dsh-codex-computer-use?
@Han-1413141/dsh-codex-computer-use 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 @Han-1413141/dsh-codex-computer-use?
Run dsh plugin --profile web add github:Han-1413141/dsh-codex-computer-use#v0.1.4 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-16 (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.
