adithyanraj03/dsh-graft-plugin
C3A DeepSeek Harness plugin that puts graft — a prebuilt graph of every symbol, its file:line span, and who calls what — in front of both you and the model.
★ 1+ · adithyanraj03/dsh-graft-plugin source on GitHub · this plugin in the registry
adithyanraj03/dsh-graft-plugin 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, uses eval / new Function.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| runs code at install time | install_script | postinstall: node scripts/postinstall.mjs |
| executes system commands | exec | ×7 in authored code, e.g. scripts/postinstall.mjs:24, scripts/postinstall.mjs:57 |
| uses eval / new Function | eval | ×1 in authored code, e.g. scripts/test-harness.mjs:451 |
Tool registrations
1 confirmed registration point(s); analysis is incomplete.
src/graft-tools.js:224tool factorysrc/index.js:725Cannot establish the tools service binding
Services it injects
remote slots tools
Hooks it attaches
agent/created agent/disposed agent/turn-stopping tools/execute
Environment variables it reads
DSH_GRAFT_SKIP_POSTINSTALL Path DSH_HOME USERPROFILE
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.