runzhliu/deepseek-harness-docker
C3Community Docker and Kubernetes packaging for DeepSeek Harness (@deepseek-ai/dsh), with a hardened image, Compose stack, Helm chart, Web UI, and headless CLI.
★ 100+ · runzhliu/deepseek-harness-docker source on GitHub · this plugin in the registry
runzhliu/deepseek-harness-docker is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, executes system commands, starts a network server.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| can rewrite the system prompt | prompt_surface | systemPrompt, webServer |
| executes system commands | exec | ×13 in authored code, e.g. scripts/capture-readme.cjs:2, scripts/capture-readme.cjs:2 |
| starts a network server | net_server | ×4 in authored code, e.g. scripts/dsh-web-relay.cjs:38, scripts/superagent-smoke.cjs:13 |
Tool registrations
2 static tool registration point(s).
plugins/dsh-alertmanager/index.js:83tools.registerplugins/dsh-browser-desktop/index.js:121tools.register
Services it injects
connection orchestrator slots systemPrompt tools webServer
Environment variables it reads
DSH_HOME DSH_UI_BROWSER_EXECUTABLE DSH_UI_PLAYWRIGHT_MODULE DSH_UI_MARKET_VERSION DSH_UI_OUTPUT DSH_WEB_RELAY_INTERFACE DSH_SUPERAGENT_PUBLIC_PORT
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.