Emilia-awa/hermes-dsh-bridge

C3

Hermes ↔ DeepSeek Harness MCP bridge: drive dsh agents (tasks, sessions, files, presets, stats) from any MCP client. Hermes = brain, Harness = arms.

★ 5+ · Emilia-awa/hermes-dsh-bridge source on GitHub · this plugin in the registry

Emilia-awa/hermes-dsh-bridge is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, runs code at install time, executes system commands, starts a network server.

Installable plugin — declares a dsh.bundle manifest

What it can do

CapabilityFlagEvidence
patches the dsh runtimeruntime_patch./cordis.patch.yml
runs code at install timeinstall_scriptpostinstall: node scripts/link-host-deps.mjs || echo "[hermes-dsh-bridge] postinstall: link-host-deps 未成功(多半是找不到 Harness 全局树)—— 请手动跑 `node scripts/link-host-deps.mjs`,或看 README「dual-package hazard」一节。
executes system commandsexec×37 in authored code, e.g. scripts/check-build-artifacts.mjs:23, scripts/check-build-artifacts.mjs:23
starts a network servernet_server×1 in authored code, e.g. src/index.ts:5642
reads credential-class env varstoken_envDSH_MCP_TOKEN

Tool registrations

0 static tool registration point(s).

Services it injects

agentPresets agents llm sessionPersistence sessions tools workspaceRegistry

Hooks it attaches

approval/request user-questions/request

Environment variables it reads

TSDOWN_BIN DSH_SESSIONS_DIR DSH_HOME DSH_HOST_TREE DSH_MCP_TOKEN

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.