yumimanji/dsh-ui-spec
C3DeepSeek Harness plugin: turn UI screenshots into structured, implementation-grade web frontend specs. Deterministic geometry (sharp) + optional vision-model semantics, merged into one JSON + Markdown
★ 1+ · yumimanji/dsh-ui-spec source on GitHub · this plugin in the registry
yumimanji/dsh-ui-spec is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, reads credential-class env vars.
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes system commands | exec | ×2 src, e.g. src/ocr-runtime.ts:2, src/ocr.ts:1 |
| reads credential-class env vars | token_env | DEEPSEEK_API_KEY, DSH_UI_SPEC_VISION_API_KEY, OPENAI_API_KEY |
Services it injects
tools
Outbound domains
api.deepseek.com
Environment variables it reads
DSH_UI_SPEC_OCR_PROBE_TIMEOUT_MS DSH_UI_SPEC_ALLOW_VISION_FALLBACK DSH_UI_SPEC_OCR_TIMEOUT_MS DSH_UI_SPEC_VISION_API_KEY DEEPSEEK_API_KEY OPENAI_API_KEY DSH_UI_SPEC_VISION_MODEL DSH_UI_SPEC_VISION_BASE_URL DSH_UI_SPEC_VISION_TIMEOUT_MS
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.