liangchen-harold/local-dsh
C3★ 5+ · liangchen-harold/local-dsh source on GitHub · this plugin in the registry
liangchen-harold/local-dsh is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, uses eval in development tooling the package does not ship, 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 system commands | exec | ×5 in authored code, e.g. scripts/run.mjs:23, scripts/run.mjs:23 |
| uses eval in development tooling the package does not ship | eval_tooling | ×1 in development tooling the package does not ship, e.g. packages/local-dsh/scripts/build.mjs:57 |
| reads credential-class env vars | token_env | APPLE_API_KEY, APPLE_API_KEY_PATH, LOCAL_DSH_CONTROL_TOKEN |
Services it injects
agentDefaultModel locale settings slots webServer
Environment variables it reads
LOCAL_DSH_RELEASE_BUILD GITHUB_HEAD_REF GITHUB_REF_NAME CI_COMMIT_REF_NAME APPLE_SIGNING_IDENTITY LOCAL_DSH_PROFILE_MANIFEST APPLE_API_ISSUER APPLE_API_KEY APPLE_API_KEY_PATH LOCAL_DSH_CONTROL_URL
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.