HRuiCcc/RuiC-dsh-purge
C2DSH 本机维护插件:预检 → 快照 → 原子写入 → 冲突检测回滚;含提示词管理与设置面板。基于 ZiPengWei/dsh-purge(MIT)。
★ 10+ · HRuiCcc/RuiC-dsh-purge source on GitHub · this plugin in the registry
HRuiCcc/RuiC-dsh-purge is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, command execution in build output only, executes commands in development tooling the package does not ship.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| can rewrite the system prompt | prompt_surface | systemPrompt |
| command execution in build output only | exec_bundled | ×3 in build output only, e.g. lib/paths.js:4, lib/paths.js:4 |
| executes commands in development tooling the package does not ship | exec_tooling | ×11 in development tooling the package does not ship, e.g. scripts/check.mjs:2, scripts/check.mjs:2 |
Tool registrations
1 static tool registration point(s).
lib/index.js:57tools.register
Services it injects
slots systemPrompt tools
Environment variables it reads
DSH_PERMISSION_MODE DSH_BASE DSH_HOME
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.