dsh-ssh/dsh-ssh
C3SSH remote workspaces for DeepSeek Harness — run bash, file, and search tools on any remote machine.
★ 10+ · dsh-ssh/dsh-ssh source on GitHub · this plugin in the registry
dsh-ssh/dsh-ssh is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes commands in development tooling the package does not ship, decodes base64 payloads, reads credential-class env vars.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes commands in development tooling the package does not ship | exec_tooling | ×3 in development tooling the package does not ship, e.g. packages/dsh-ssh/scripts/build-readme.mjs:5, packages/dsh-ssh/scripts/build-readme.mjs:5 |
| decodes base64 payloads | base64_decode | ×3 in authored code, e.g. packages/dsh-ssh/client.js:2242, packages/dsh-ssh/src/remote.js:296 |
| reads credential-class env vars | token_env | SSH_AUTH_SOCK |
Services it injects
fs locale remote shell slots tools workspaces
Hooks it attaches
agent/created connection/reset domain/changed
Environment variables it reads
DSH_HOME SSH_AUTH_SOCK
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.