PerryLink/dsh-github
C3Official-grade GitHub CI for DeepSeek Harness: composite action.yml, PR review bot with idempotent inline comments and a status-check gate, plus PR/issues tools with every write gated by human approva
★ 1+ · PerryLink/dsh-github source on GitHub · this plugin in the registry
PerryLink/dsh-github is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, gates tool execution, executes system commands, decodes base64 payloads.
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| gates tool execution | tool_gate | hook: tools/pre-execute |
| executes system commands | exec | ×10 src, e.g. lib/credential.js:12, lib/git.js:8 |
| decodes base64 payloads | base64_decode | ×2 src, e.g. lib/tools.js:1279, src/tools.ts:1370 |
| reads credential-class env vars | token_env | DEEPSEEK_API_KEY, DSH_GITHUB_TOKEN, GITHUB_TOKEN |
Services it injects
approval commands credentials jobs tools
Hooks it attaches
tools/pre-execute
Outbound domains
api.github.com
Environment variables it reads
RUNNER_TEMP GITHUB_WORKSPACE GITHUB_OUTPUT DSH_GITHUB_CI_DRIVER DEEPSEEK_API_KEY DSH_GITHUB_CI_OUTPUT_DIR INPUT_OUTPUT_DIR INPUT_BLOCKING DSH_GITHUB_TOKEN GITHUB_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.