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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.Install verification details →
Data as of (UTC)
What it doesAI
A plugin that wraps a mini-agent's tool surface as native DeepSeek Harness tools.
- Provides a mini-agent tool surface as native DSH tools
- Written in DSH form for DeepSeek Harness
- Re-registers mini-agent tools for seamless integration
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 dsh-kernel-minimaxInstall method: npm · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.2-rc.3
Trends
Four lines, four questions: total stars, stars gained this week, cumulative downloads, downloads this week. The GitHub pair comes from real-read sampling — a rotating daily shard, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
9 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-13 · 9 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
10-02 → 11-13 · 8 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-07 → 11-17 · 65 points
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
09-07 → 11-17 · 65 points
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.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 0.1.8 | ○ | ○ | ○ | ○ | ○ |
| 0.1.2 | · | · | · | · | · |
| v0.1.2 | · | · | · | · | · |
0.1.8npm○ 16 ecosystem plugin2026-11-15
dsh-kernel-minimax
○dsh 0.2.2-rc.32026-11-15Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-15 · expires: 2026-11-22
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.2-rc.12026-11-06Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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-rc.52026-11-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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-rc.32026-10-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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-rc.22026-10-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
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: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.2.1-alpha.4 · profile: l4-sandbox
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-12Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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.0-rc.22026-10-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.1.7-rc.22026-09-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
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.1.7-rc.12026-09-24Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
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.1.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
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.1.6-alpha.12026-09-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.1.5-rc.22026-09-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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.1.3-alpha.22026-09-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
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.1.3-alpha.12026-09-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
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.
○prehistory2026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-kernel-minimax@0.1.8
ID: dsh-kernel-minimax@0.1.8@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
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.
0.1.2npm2026-09-08
dsh-kernel-minimax
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L4 · Ecosystem plugin (the not-bundle verdict comes from the install step; L5 does not apply). The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
v0.1.2github○ 2 ecosystem plugin2026-09-07
https://github.com/oppnc/dsh-kernel-minimax
○dsh 0.1.3-alpha.12026-09-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/oppnc/dsh-kernel-minimax#v0.1.2
ID: dsh-kernel-minimax@v0.1.2@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.2-rc.12026-09-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/oppnc/dsh-kernel-minimax#v0.1.2
ID: dsh-kernel-minimax@v0.1.2@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
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/dsh-kernel-minimax/?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 medium (authoritative when present) → overall medium.
v0.1.80.1.8npm2026-11-190.1.8same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (1)
- criticalpipeShell · shell
lib/system-prompt.js:574. If uv missing: \`curl -LsSf https://astral.sh/uv/install.sh | sh\`
show 4 audit findings
- mediumbash tool gives the model un-mediated arbitrary PowerShell execution with no in-plugin approval or policy
lib/index.js:231A single tool call runs any command with the host process privileges (spawn at lines 249/269 passes only cwd/stdio, no policy object), so prompt-injected content read by the model can drive command execution, file destruction or data exfiltration. The only in-plugin constraint is a working directory that may silently degrade: policyFor() returns undefined on any error (line 86) and cwdOf() then falls back to process.cwd() or 'C:\\' (lines 91-93), and pwsh resolution failures fall back to a hardcoded powershell.exe path (line 229-230). No permission/approval metadata is declared at tools.regist
- lowShipped system prompt tells the agent to pipe a remote installer script into a shell
lib/system-prompt.js:57Because the persona is installed with complete:true, this text is effectively the agent's only instruction set; whenever Python tooling is needed the model is directed to download and execute an unpinned remote script through the bash tool, an avoidable supply-chain execution path that bypasses any package-manager verification.
- lowPersona section is installed with complete:true and suppresses the host runtime context
lib/index.js:75By default (unless config.skipPersona is set) the plugin makes its own text the sole system-prompt section (complete: true, line 73) and drops the runtime-context snapshot, so any host-injected safety, sandbox or tool-usage guidance is removed from the model's context before the same session is handed a shell tool. The change is silent and on by default for anyone mounting this kernel.
- lowFile reads bypass the sandbox policy used for writes, and policy resolution fails open
lib/index.js:159write_file/edit_file pass the resolved sandbox policy to the fs service while read_file (and fs.resolve at line 158) passes none, so path confinement for reads depends entirely on host defaults. Combined with policyFor()'s silent catch returning undefined (line 86) and cwdOf()'s fallback to process.cwd() (line 92), a host without sandboxPolicy loses confinement rather than failing closed, and model-chosen paths can be resolved relative to the process directory.
No backdoor or exfiltration found; residual risk is the intended but un-gated PowerShell tool plus a prompt that replaces host context and tells the agent to curl|sh.
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-08-31 · activity: Stable
• Repo created: 2026-08-13
• Stars: ★ 1 · Forks: 0
• Health: Stable — committed within 90 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).
Frequently asked questions
What is dsh-kernel-minimax?
dsh-kernel-minimax 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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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 dsh-kernel-minimax?
Run dsh plugin --profile web add dsh-kernel-minimax 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. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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-19 (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.
