Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
DSH adapter that registers 11 context-mode ctx_* sandbox tools in-process with hook routing to cut session context usage.
- Registers 11 ctx_* tools in-process: sandbox exec, FTS5 index/search, batch, fetch-and-index
- Hook pre-intercepts large tool outputs and injects per-turn routing blocks
- Settings card shows status, one-click doctor check and tool on/off toggles
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:sadjjk/dsh-context-mode-adapter#v0.1.1Install method: GitHub · runtime verified (L5)
Verification & Compatibility
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.2 |
|---|---|---|
| v0.1.1 | ✓ | ✓ |
v0.1.1github✓ 2 runtime-verified2026-10-20
https://github.com/sadjjk/dsh-context-mode-adapter
✓dsh 0.2.1-rc.2current2026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/sadjjk/dsh-context-mode-adapter#v0.1.1
ID: dsh-context-mode-adapter@v0.1.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.1-alpha.22026-10-14L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/sadjjk/dsh-context-mode-adapter#v0.1.1
ID: dsh-context-mode-adapter@v0.1.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-context-mode-adapter/)``[](https://www.dsh.so/artifact/dsh-context-mode-adapter/)`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 — stricter wins → overall low.
v0.1.1dsh manifestv0.1.1git2026-10-21v0.1.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalnewFunction · code-exec
lib/index.js:848schema.callback = new Function("return " + schema.callback)(); - criticalshellExec · shell
lib/index.js:20const p = execSync("which context-mode", { - criticalshellExec · shell
lib/index.js:27const prefix = execSync("npm config get prefix", { - criticalshellExec · shell
lib/index.js:45const dirs = execSync(`ls -d ${nvmBin}/*/bin/context-mode 2>/dev/null`, {
show 4 audit findings
- lownvm probe interpolates a home-derived path into a shell command
lib/index.js:45The nvm fallback builds a shell string from join(homedir(), '.nvm/versions/node'). If HOME ever contains shell metacharacters (spaces, $(...), ;) the command would be reparsed by the shell. Requires a pre-existing attacker-influenced HOME plus existence of that directory, so impact is marginal; the other two execSync calls are fully constant strings.
- lowIn-process import of a PATH-resolved 'context-mode' package not declared in package.json
lib/index.js:373resolvePackageRoot() follows detectContextModePath() (`which context-mode`) and imports build/server.js from whatever package named context-mode it finds, then registers its handlers as kernel tools that execute with the host's privileges. context-mode is not listed in dependencies/peerDependencies, so the resolved artifact is whatever is installed on PATH / globally. This is the plugin's documented design (UI tells the user to npm install -g context-mode), so the residual risk is supply-chain rather than an exploitable flaw.
- lowBundled schemastery contains new Function() on schema.callback (unreachable here)
lib/index.jsThis is dead code from the vendored @deepseek-ai/schemastery build. schema.callback is only assigned a string by transform()-style schemas; this plugin's Config uses only Schema.boolean()/Schema.number()/Schema.object with literal defaults, so no string ever reaches new Function. No dynamic evaluation of plugin, user or model input occurs.
- lowPredictable /tmp sentinel path written without exclusive/no-follow flags
lib/index.js:540On multi-user POSIX hosts another local user can pre-create /tmp/context-mode-mcp-ready-<pid> as a symlink; writeFileSync follows it, so the plugin would overwrite the link target with the pid digits, and unlinkSync on exit would remove the link. Content is trivial (a pid) and the pid is guessable only within the process lifetime, so impact is limited to clobbering a file the attacker already controls the link for.
Static 'critical' hits are heuristic: execSync commands are fixed, the bundled new Function is unreachable, writes stay in ~/.dsh; only low-risk hardening gaps remain.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-10-09 · activity: Active
• Repo created: 2026-10-09
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
