Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Supports vibe coding by saving answers for later and using side chats/related conversations without losing focus.
- Save answers for later use while coding
- Side Chat for spontaneous questions
- Open related conversations for deeper work
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-branchmarkInstall method: npm · 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
Based on 1 requirement(s) across 22 @deepseek-ai/dsh-* packages. raw ranges
0.1.2-rc.1 ×22
✗ Running dsh 0.2.1-rc.2 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-branchmark@0.1.2-rc.2 0.2.1-rc.2 (the exemption lives in the local profile; this site does not assume one)
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| 0.1.2-rc.2 | ✓ | ✓ | ✓ | ✓ | ✓ |
| v0.1.1-rc.2 | · | · | · | · | · |
0.1.2-rc.2npm✓ 12 runtime-verified2026-10-18
dsh-branchmark
✓dsh 0.2.1-rc.2current2026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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.42026-10-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
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-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
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.0-rc.22026-10-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
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.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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.1.7-rc.22026-09-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dsh0.1.7-rc.2 · profile: l3-fullscan
Issued: 2026-09-25 · expires: 2026-10-02
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.1.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-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.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.1.5-rc.22026-09-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
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.1.3-alpha.22026-09-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
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.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-branchmark@0.1.2-rc.2
ID: dsh-branchmark@0.1.2-rc.2@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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.
v0.1.1-rc.2github2026-09-08
https://github.com/zaizaizhao/dsh-branchmark
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-branchmark/)``[](https://www.dsh.so/artifact/dsh-branchmark/)``[](https://www.dsh.so/artifact/dsh-branchmark/)``[](https://www.dsh.so/artifact/dsh-branchmark/)``[](https://www.dsh.so/artifact/dsh-branchmark/)``[](https://www.dsh.so/artifact/dsh-branchmark/)`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.
v0.1.2-rc.2dsh manifest0.1.2-rc.2npm2026-10-240.1.2-rc.2same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (1)
- criticalnewFunction · code-exec
lib/index.js:247schema.callback = new Function("return " + schema.callback)();
show 2 audit findings
- lowVendored schemastery `new Function` can evaluate string callbacks, but no plugin path supplies one
lib/index.js:247Dynamic code evaluation from a bundled dependency. It only fires when a Schema node is constructed with a string `callback`, i.e. when a schema is deserialized from external JSON. The plugin's only schema is `static Config = Schema.object({...})` composed of `Schema.number()...` nodes, and no Remote method accepts a schema or callback field, so the branch is unreachable with attacker-controlled input in this build; the host region that would need it (lib/typert.host.js) was not harvested, so this is recorded as refuted rather than exploitable.
- lowproject_search reads discovered entries without re-applying the project containment check
lib/index.jsproject_read/project_list resolve their argument and explicitly call ctx.fs.contains(root, target), but project_search walks children via raw listDir entries (item.target) and reads them without repeating that check. If the workspace contains a symlink to a directory or file outside the project, matching lines from that target can be returned to the model, i.e. an out-of-project read via an existing symlink. It is read-only, bounded (maxSearchFiles/maxReadChars/100 matches, .git and node_modules skipped) and requires such a symlink to pre-exist in the workspace.
Danger signal is a vendored schemastery `new Function` that this plugin never reaches; project file tools stay inside the project root, leaving only low-severity hardening gaps.
Rule (2026-10-24): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); without one, the static/vet fused tier applies. 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 static/vet.
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-08 · activity: Active
• Repo created: 2026-08-30
• Stars: ★ 25 · 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).