Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
CLI tool that scripts a running DSH instance: creates workspace sessions, sends prompts, and reads back conversations and injected memory.
- Create sessions in the correct workspace from scripts
- Send prompts to a running DSH instance automatically
- Read back conversations and injected memory for inspection
Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.
Installation
dsh plugin --profile web add github:D120697/dshctlInstall method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.2-rc.1 current |
|---|---|
| d64ae6 | · |
| bdd81a | ○ |
d64ae6local2026-11-10
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
bdd81agithub○ 1 ecosystem plugin2026-11-10
https://github.com/D120697/dshctl
○dsh 0.2.2-rc.1current2026-11-10Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/D120697/dshctl#bdd81a60faa41614abf673de64774ef23e389f4b
ID: dshctl-3@bdd81a60faa41614abf673de64774ef23e389f4b@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-10 · expires: 2026-11-17
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dshctl-3@d64ae6@dsh0.2.2-rc.1 (l3-fullscan)
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Author badges
Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dshctl-3/?ref=badge)`dsh.so is an independent community project, not affiliated with or endorsed by DeepSeek AI. Badges are maintained by dsh.so; embed links carry a ?ref= attribution parameter.
Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static low; dynamic low (authoritative when present) → overall low.
—bdd81a60faa4git2026-11-11bdd81a60faa4same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- warningnetIp · network
dshctl.py:96f"http://127.0.0.1:{port}/api/session/list", - warningnetIp · network
dshctl.py:167url = f"http://127.0.0.1:{port}/?token={urllib.parse.quote(token, safe='')}"
show 1 audit findings
- lowMints a 30-day auth cookie from the local signing secret instead of preferring the launch token
dshctl.py:185When no --token is supplied, build_cookie() reads the HMAC secret from ~/.dsh/.credentials.yaml and forges a browser-session cookie valid for 30 days against the local authority. The secret itself is never sent (only an HMAC over a JSON payload), and the target is always 127.0.0.1, so no exfiltration occurs; however it bypasses the user-gesture/token flow and houses a long-lived credential in shell history-free memory, and a --port pointed at a rogue local listener would receive a validly signed cookie.
Loopback-only DSH CLI: fixed subprocess binaries, all HTTP targets 127.0.0.1, HMAC secret never leaves the host; only minor hardening gaps.
Rule (2026-10-28): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); the static scan tier (vet primary, dsh backstop) applies only when there is none (not queued / audit failed / withdrawn). The audit never writes the exemption list (exemptions are manual only); a wrong conclusion is withdrawn by human review and the tier falls back to the static scan tier.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-11-09 · activity: Active
• Repo created: 2026-11-09
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/D120697/dshctl
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
Frequently asked questions
What is @D120697/dshctl?
@D120697/dshctl is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
Is dsh.so or this plugin page official?
dsh.so is an independent community registry and is not affiliated with, endorsed by, or sponsored by DeepSeek AI.
How do I install @D120697/dshctl?
Run dsh plugin --profile web add github:D120697/dshctl in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
How does the security scan relate to a manual audit?
Both layers are automated, not a manual audit. The static scan is heuristic analysis of the repository source, so it can produce false positives and miss context. The model-driven dynamic security audit only covers plugins static-flagged at warn or above, never executes plugin code, and its conclusion is authoritative when there is one (it may raise or lower the static tier); exemptions stay manual. Neither layer is an endorsement: review the repository and the permissions it asks for before installing, together with the verification level and health signals.
How fresh is the data on this page?
The data on this page is as of 2026-11-11 (UTC) — the most recent valid timestamp among the registry refresh, install verification, security scan and dynamic audit. Build time is never used as a data date.