pax-beehive/dsh-hub-cli
C3Open-source CLI, schemas, resolver, and DSH agent tools for DSH Plugin Hub
★ 100+ · pax-beehive/dsh-hub-cli source on GitHub · this plugin in the registry
pax-beehive/dsh-hub-cli is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, decodes base64 payloads, reads credential-class env vars.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes system commands | exec | ×15 in authored code, e.g. scripts/verify-package-contents.mjs:1, scripts/verify-package-contents.mjs:1 |
| decodes base64 payloads | base64_decode | ×1 in authored code, e.g. packages/cli/src/profile-dependency-lock.ts:138 |
| reads credential-class env vars | token_env | DSH_HUB_TOKEN |
Services it injects
tools
Outbound domains
api.workos.com api.dshpluginhub.ai dshpluginhub.ai
Environment variables it reads
DSH_HUB_MACHINE DSH_HUB_API_URL NODE_EXTRA_CA_CERTS SSL_CERT_FILE SSL_CERT_DIR RELEASE_TAG GITHUB_REF_NAME DSH_HUB_WORKOS_CLIENT_ID DSH_HUB_TOKEN DSH_HUB_TELEMETRY
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.