runseal-labs/dsh-tool-runseal
C3RunSeal 沙箱插件:为 dsh 提供 OS 原生策略执行边界(Windows/macOS/Linux) | RunSeal sandbox provider for DeepSeek Harness — OS-native policy-enforced command execution
★ 0 · runseal-labs/dsh-tool-runseal source on GitHub · this plugin in the registry
runseal-labs/dsh-tool-runseal 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, powerful capability in test/example code only.
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/install.mjs |
| executes system commands | exec | ×10 in authored code, e.g. scripts/prepare-desktop-ptc.mjs:2, scripts/prepare-desktop-ptc.mjs:2 |
| powerful capability in test/example code only | dev_surface | in code that does not ship: sandbox, subprocess |
Tool registrations
0 static tool registration point(s).
Services it injects
configForms slots
Outbound domains
api.github.com
Environment variables it reads
ELECTRON_RUN_AS_NODE RUNSEAL_BINARY LOCALAPPDATA RUNSEAL_SKIP_DOWNLOAD ComSpec RUNSEAL_WINDOWS_SANDBOX_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.