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
Windows-native computer-use plugin that runs find/click/type/wait/screenshot batches in one round trip without stealing focus or pointer.
- Batches find/click/type/wait/screenshot in one tool call
- Drives Windows apps without taking focus or pointer
- Cuts model round trips for desktop automation
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.
6 samples (roughly every 7 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
09-21 → 11-01 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-01 → 11-01 · 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
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:wwwort/dsh-win-computer-use#v0.1.1Install method: GitHub · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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 a single engines.dsh range (decides alone; peerDependencies is not consulted). raw ranges
>=0.1.0-rc.1 <0.2.0-0
✗ Running dsh 0.2.2-rc.1 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-win-computer-use-3@0.1.1 0.2.2-rc.1 (the exemption lives in the local profile; this site does not assume one)
Deciding channel: since 0.2.1-alpha.4 DSH judges by engines.dsh when declared — peerDependencies is then not consulted.
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.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| v0.1.1 | ✗ | ✗ | ✓ | ✓ | ✓ |
| v0.1.0 | · | · | · | · | · |
v0.1.1github✓ 7 runtime-verified2 failed2026-11-04
https://github.com/wwwort/dsh-win-computer-use
✗dsh 0.2.1-rc.52026-10-31L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/wwwort/dsh-win-computer-use#v0.1.1
ID: dsh-win-computer-use-3@v0.1.1@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (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-26L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/wwwort/dsh-win-computer-use#v0.1.1
ID: dsh-win-computer-use-3@v0.1.1@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/wwwort/dsh-win-computer-use#v0.1.1
ID: dsh-win-computer-use-3@v0.1.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (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.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/wwwort/dsh-win-computer-use#v0.1.1
ID: dsh-win-computer-use-3@v0.1.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (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/wwwort/dsh-win-computer-use#v0.1.1
ID: dsh-win-computer-use-3@v0.1.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (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/wwwort/dsh-win-computer-use#v0.1.1
ID: dsh-win-computer-use-3@v0.1.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (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.12026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/wwwort/dsh-win-computer-use#v0.1.1
ID: dsh-win-computer-use-3@v0.1.1@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (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.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/wwwort/dsh-win-computer-use#v0.1.1
ID: dsh-win-computer-use-3@v0.1.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (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/wwwort/dsh-win-computer-use#v0.1.1
ID: dsh-win-computer-use-3@v0.1.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (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.
v0.1.0github✓ 1 runtime-verified2026-09-20
https://github.com/wwwort/dsh-win-computer-use
✓dsh 0.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/wwwort/dsh-win-computer-use#v0.1.0
ID: dsh-win-computer-use-3@v0.1.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-win-computer-use-3@v0.1.1@dsh0.2.2-rc.1 (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.
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:
`[](https://www.dsh.so/artifact/dsh-win-computer-use-3/?ref=badge)``[](https://www.dsh.so/artifact/dsh-win-computer-use-3/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-win-computer-use-3/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-win-computer-use-3/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-win-computer-use-3/?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.1dsh manifestv0.1.1git2026-11-05v0.1.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningchildProcess · code-exec
lib/bridge.js:176const child = spawn(this.config.powershell, [ - warningchildProcess · code-exec
lib/bridge.js:327const child = spawn(this.config.powershell, [ - warningshellExec · shell
scripts/preflight.mjs:85const raw = execSync('npm pack --dry-run --json', { - warningchildProcess · code-exec
src/bridge.ts:214const child = spawn( - warningchildProcess · code-exec
src/bridge.ts:369const child = spawn(
show 5 audit findings
- mediumLoopback engine daemon accepts any local client and trusts a temp-dir port file
lib/bridge.js:268The payload protocol has no token, nonce or peer validation, and the port is published in `join(tmpdir(),'dsh-computer-use','daemon-port.txt')`, which is read back and trusted on startup (`const existing = this.readPortFile();`). Any local process can (a) connect to the daemon and drive the user's desktop — clicks, keystrokes, clipboard reads, screenshots — as the logged-in user, or (b) pre-create/overwrite the port file to impersonate a warm daemon and receive every later step payload, including the exact `text` the model types (which may be a secret typed into a form).
- mediumModel-reachable process start/stop and physical input with no confirmation gate
lib/index.js:73Any model output (or any content the model has read via the `read` op, i.e. untrusted window/webpage text) can start an arbitrary executable by path, stop arbitrary processes, and inject keystrokes/mouse into arbitrary windows. The JS layer performs no validation, allowlist or user-confirmation step, so screen content that hijacks the model becomes an arbitrary program-execution and input-injection primitive on the real desktop.
- lowDaemon-reported pid from an unauthenticated peer is used in process.kill
lib/bridge.js:227`probe()` stores whatever pid the (unauthenticated) loopback peer reports, and `killDaemon()` later calls `process.kill()` on it on any io-phase failure or 'stale' verdict. A local process that answers the ping can nominate an arbitrary pid and have the plugin terminate that process as the user.
- lowModel-controlled screenshot path is written to disk and then read back into the conversation
lib/index.jsThe engine writes the captured PNG to a model-supplied absolute path, so a step (or a prompt-injected page) can overwrite any file the user can write with PNG bytes. The same path is then read back by `inlineImage` and uploaded as an attachment, so if the engine echoes a path it did not actually write, an arbitrary readable file could be pulled into the transcript.
- lowThe PowerShell engine that performs every sensitive action is not in the audited source
lib/bridge.js:177`scripts/win.ps1` is spawned with execution policy bypassed and receives every step payload, yet it is absent from the submitted file set (the harvest contains only scripts/preflight.mjs). Process start/stop, keystroke injection, clipboard access, screenshots and file writes are all implemented there, so none of the guardrails implied by the JS layer can be verified, and if the file is genuinely missing from the tarball the tool fails on first use (`engine script is missing`).
Windows desktop-automation plugin works as designed; residual risk is an unauthenticated loopback engine daemon that trusts a temp port file, plus an engine script that ships but is not in the audited source.
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-19 · activity: Stable
• Repo created: 2026-09-19
• Stars: ★ 0 · 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 @wwwort/dsh-win-computer-use?
@wwwort/dsh-win-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 @wwwort/dsh-win-computer-use?
Run dsh plugin --profile web add github:wwwort/dsh-win-computer-use#v0.1.1 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-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.
