wanghongjian0119/deepseek-harness-desktop
C2Community MIT fork of DeepSeek Harness with a Linux-only desktop shell (.deb and AppImage). Not an official DeepSeek release.
★ 0 · wanghongjian0119/deepseek-harness-desktop source on GitHub · this plugin in the registry
wanghongjian0119/deepseek-harness-desktop is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It runs code at install time, executes system commands, decodes base64 payloads, reads credential-class env vars.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| runs code at install time | install_script | postinstall: node scripts/ensure-spawn-helper.mjs |
| executes system commands | exec | ×86 in authored code, e.g. apps/desktop/scripts/desktop-build-commit.mjs:10, apps/desktop/scripts/desktop-build-commit.mjs:10 |
| decodes base64 payloads | base64_decode | ×3 in authored code, e.g. apps/desktop/scripts/prepare-installed-update-network.ts:47, apps/desktop/scripts/smoke-runtime.ts:80 |
| reads credential-class env vars | token_env | CSC_KEYCHAIN, DSH_DESKTOP_WINDOWS_KEY_CONTAINER, DSH_DESKTOP_WINDOWS_TOKEN_PIN |
| powerful capability in test/example code only | dev_surface | in code that does not ship: systemPrompt, webServer |
Hooks it attaches
connection/request
Outbound domains
download-test.deepseek.com download.deepseek.com test.example.com login.example.com timestamp.digicert.com
Environment variables it reads
DSH_DESKTOP_PACKAGING_RUN_DIR DSH_CLIENT_VERSION npm_execpath DSH_DESKTOP_OPEN_DEVTOOLS SystemRoot DSH_DESKTOP_PRIMARY_RUNTIME_DIR DSH_DESKTOP_WINDOWS_SIGNTOOL DSH_TELEMETRY_DISABLED DSH_HOME DSH_DESKTOP_USER_DATA_DIR
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.