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 →
What it doesAI
Adds a run_kernel_code tool to DSH, running persistent Python and JavaScript kernels whose state survives across calls.
- Exposes a run_kernel_code tool for DSH
- Runs long-lived python3/node kernels per session
- Variables and state persist across successive calls
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:hy-sde/dsh-code-runtime-kernelsInstall 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
○ 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.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|
| 6ffeba | ○ | ○ | ○ |
| 5a9f7c | · | · | · |
6ffebagithub○ 3 ecosystem plugin2026-10-19
https://github.com/hy-sde/dsh-code-runtime-kernels
○dsh 0.2.1-rc.2current2026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/hy-sde/dsh-code-runtime-kernels (version unstated)
ID: dsh-code-runtime-kernels@6ffeba@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
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.
○dsh 0.2.1-alpha.42026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/hy-sde/dsh-code-runtime-kernels (version unstated)
ID: dsh-code-runtime-kernels@6ffeba@dsh0.2.1-alpha.4 · profile: l3-fullscan
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
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.
○dsh 0.2.1-alpha.22026-10-14Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/hy-sde/dsh-code-runtime-kernels (version unstated)
ID: dsh-code-runtime-kernels@6ffeba@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
View checks & evidence
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.
5a9f7clocal2026-10-14
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-code-runtime-kernels/)`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.7-rc.20.1.7-rc.2git2026-10-210.1.7-rc.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (3)
- criticaleval · code-exec
packages/code-runtime-kernels/src/python/runner.ts:491return await eval(code_obj, ns) - criticaleval · code-exec
packages/code-runtime-kernels/src/python/runner.ts:492return eval(code_obj, ns) - warningchildProcess · code-exec
packages/code-runtime-kernels/src/core/kernel.ts:323const proc = spawn(wrapped[0] ?? profile.command, wrapped.slice(1), {
show 2 audit findings
- lowModel code in the kernel inherits the full host environment (process.env)
packages/code-runtime-kernels/src/index.tsAny credential in the harness process environment (model/API keys, tokens) is readable by model-generated kernel code and can be echoed back in logs or the completion value; with sandboxConfinement defaulting to false the kernel can also reach the network. This is consistent with the plugin's documented bash-equivalent trust model, hence low, but the model-facing tool description never mentions it.
- lowNamespace snapshots are Python pickle deserialized by the kernel from a user-writable directory
packages/code-runtime-kernels/src/python/runner.tsRestoring a session snapshot executes pickle opcodes. The file path is ~/.dsh/code-runtime-kernels/state/<lang>/<sha256(lang:sessionId)>.snapshot, and session ids are model-chosen, so code running in one kernel (or anything running as the same unix user) can pre-plant another session's snapshot and get code execution in that kernel on its next restore. No privilege escalation is gained — the attacker already runs with bash-equivalent trust — so this is a low-severity state-injection/integrity gap; the code comments acknowledge pickle is not a security boundary.
Persistent Python/JS kernel tool that runs model code in spawned subprocesses by design; host-side frame validation and process-group teardown are solid, leaving only low-severity env/pickle exposure.
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-16 · activity: Active
• Repo created: 2026-08-20
• 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).
