What it does
Deepseek harness desktop package. all origin, not modify
Installation
dsh plugin --profile web add github:diamondfsd/deepseek-harness-desktopInstall method: GitHub · not yet tested in container (L3+)
Compatibility
| DSH Version | Status |
|---|---|
| not stated | Declared — not tested |
Requirements
- • Node.js: not stated
- • DSH: declared "not stated"
- • External credentials: none detected
Security Report
Automated static scan, not manual review.
Critical findings in non-blocking categories (dynamic code execution, shell execution, install scripts, obfuscation). Common in CLI/terminal plugins but worth reviewing.
code-exec ×6shell ×10.1.0-rc.7172d3f06b2272026-08-19172d3f06b227The scan result is only valid for the scanned commit. If the latest commit differs, the badge shows outdated until the daily pipeline rescans.
Disclaimer: automated static analysis, not a security guarantee. Always review what you install.
• Static heuristic scan: done (15 files)
• Dependency vulnerabilities: requires deep audit (L3+)
• Permission sandboxing: requires runtime testing (L4+)
High-risk findings · 8 / 8
- criticalChild process module usage (Node.js)scripts/generate-icon.mjs:1import { execFileSync } from 'node:child_process'
- criticalShell command execution (exec / execSync)scripts/generate-icon.mjs:13execFileSync(command, args, { stdio: 'inherit' })
- criticalChild process module usage (Node.js)scripts/package.mjs:1import { spawnSync } from 'node:child_process'
- criticalChild process module usage (Node.js)scripts/resolve-upstream.mjs:5import { spawnSync } from 'node:child_process'
- criticalChild process module usage (Node.js)scripts/sync-upstream.mjs:1import { spawnSync } from 'node:child_process'
- criticalChild process module usage (Node.js)scripts/update-upstream.mjs:1import { spawnSync } from 'node:child_process'
- criticalChild process module usage (Node.js)src/main/index.ts:2import { spawn, type ChildProcessWithoutNullStreams } from 'node:child_process'
- warningDownloads a file from the networkscripts/deploy-release.sh:247status="$(curl -sS -o "$response_file" -w '%{http_code}' -X POST "${API_BASE}/releases" \
Heuristic static scan — may produce false positives. Review the source yourself before trusting.
Activity
Last commit 2026-08-19 · activity: Active
• Repo created: 2026-08-19
• Stars: ★ 2 · Forks: 0
• Health: Active — committed within last 30 days
