rootkiller6788/dsh-launcher

C3

Unlock DeepSeek Harness plugin-native core capabilities, unifying Runtime, Provider, Plugin, Skill and MCP orchestration to build an extensible, composable and manageable local AI runtime platform.

★ 10+ · rootkiller6788/dsh-launcher source on GitHub · this plugin in the registry

rootkiller6788/dsh-launcher is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It can spawn subprocesses, executes system commands, decodes base64 payloads, starts a network server.

No dsh integration found — this repository carries the dsh-plugin topic but shows no sign of connecting to dsh

What it can do

CapabilityFlagEvidence
can spawn subprocessessubprocess_serviceinject: subprocess
executes system commandsexec×18 in authored code, e.g. scripts/push-both.mjs:31, scripts/push-both.mjs:31
decodes base64 payloadsbase64_decode×2 in authored code, e.g. tui/host/reference/lan-https-certificate.ts:305, tui/host/reference/lan-https-certificate.ts:312
starts a network servernet_server×1 in authored code, e.g. tui/host/index.js:186

Services it injects

desktopPnpmBootstrap desktopProfiles desktopRuntime subprocess

Outbound domains

gitee.com registry.npmmirror.com pypi.org cdn.jsdelivr.net electronjs.org www.dshdesktop.cn gh-proxy.com ingest.example.com

Environment variables it reads

TAURI_ENV_DEBUG AHL_NPM_MIRROR AHL_PYPI_MIRROR TRACE_LOG

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.