chenshutian9610/deepseek-harness-plugin-list
C3个人 deepseek-harness 插件集合
★ 0 · chenshutian9610/deepseek-harness-plugin-list source on GitHub · this plugin in the registry
chenshutian9610/deepseek-harness-plugin-list is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, can intercept API traffic, can spawn subprocesses, executes system commands.
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| can intercept API traffic | api_intercept | apiProxy, subprocess, webServer |
| can spawn subprocesses | subprocess_service | inject: subprocess |
| executes system commands | exec | ×7 src, e.g. packages/deepseek-harness-web/bin.mjs:2, packages/deepseek-harness-web/bin.mjs:5 |
| starts a network server | net_server | ×2 src, e.g. packages/deepseek-harness-web/check.mjs:374, packages/deepseek-harness-web/check.mjs:410 |
Services it injects
agents apiProxy cmdlineArgs credentials llm locale sandboxPolicy sessions slots subprocess theme tools webRuntime webServer webStartup
Hooks it attaches
agent/created credentials/updated internal/dispatch theme/change
Outbound domains
harness.example.com evil.example.com
Environment variables it reads
NODE_USE_ENV_PROXY
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.