wulun811/dsh-plugin-vet

C3

Trust pipeline for deepseek-harness plugins: deterministic static scan (11 rules) + LLM-driven audit protocol + two-part scorecard, with optional runtime guard (T1 sentinel / T2 fs & child_process hoo

★ 1+ · wulun811/dsh-plugin-vet source on GitHub · this plugin in the registry

wulun811/dsh-plugin-vet is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, uses eval / new Function, decodes base64 payloads.

What it can do

CapabilityFlagEvidence
patches the dsh runtimeruntime_patch./cordis.patch.yml
executes system commandsexec×38 src, e.g. scripts/e2e-local.mjs:10, scripts/e2e-local.mjs:10
uses eval / new Functioneval×1 src, e.g. scanner-bin/rules/dynamic-exec.ts:113
decodes base64 payloadsbase64_decode×1 src, e.g. scanner-bin/rules/string-heuristics.ts:29
starts a network servernet_server×2 src, e.g. scripts/verify-status-route.mjs:14, scripts/verify-status-route.mjs:41
reads credential-class env varstoken_envDEEPSEEK_API_KEY

Services it injects

locale skills slots tools

Hooks it attaches

dispose internal/plugin ready tools/execute

Outbound domains

api.osv.dev www.jsdelivr.com www.chartjs.org oauth2.googleapis.com

Environment variables it reads

DSH_PLUGIN_VET_CACHE_DIR DEEPSEEK_API_KEY VET_E2E_PROFILE DSH_PLUGIN_VET_ARCHIVE_DIR

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.