Install verification: Ecosystem app: not installed via dsh plugin add, so the L1-L5 plugin install-verification ladder does not apply; the security scan still runs.
What it does
Codex-like floating glass preview window for DeepSeek Harness background computer-use (macOS)
Installation
Ecosystem apps are not installable via dsh plugin add: desktop / web shells install or deploy through their own release channel (GitHub Releases or the project site).
The level reads L5 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (the L1-L5 ladder does not rate them); the security scan still runs.
Verification & Compatibility
No verification record yet for this plugin.
- • Node.js: not stated
- • DSH: not stated
- • External credentials: none detected
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-cua-preview-2/)`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 no conclusion — stricter wins → overall low.
v1.0.0dsh manifest1.0.0git2026-10-211.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningshellExec · shell
app/main.js:274execFile('/usr/sbin/screencapture', args, { timeout: 3000 }, (error) => { - warningfsWrite · files
app/main.js:76if (fs.statSync(LOG_FILE).size > 256 * 1024) fs.writeFileSync(LOG_FILE, '') - warningfsWrite · files
app/main.js:79try { fs.appendFileSync(LOG_FILE, `${new Date().toISOString()} ${line}\n`) } catch {} - warningfsWrite · files
app/main.js:104fs.writeFileSync(STATE_FILE, JSON.stringify({ x: bounds.x, y: bounds.y })) - warningchildProcess · code-exec
plugin/index.js:216const child = spawn(electronPath, ['--no-sandbox', options.appDir], {
not in the dynamic queue (queue only covers plugins static-flagged at warn or above) — this does not mean the dynamic audit found it safe.
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-21 · activity: Active
• Repo created: 2026-10-21
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 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).
