Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Git branch and worktree manager for DSH: shows the current branch in the input toolbar, supports switching, remote checkout, push/pull and isolated worktrees.
- Shows current branch in the input toolbar and switches in place
- IDEA-style branch picker with remote checkout and right-click menu (new/rename/delete/copy)
- Pushes and updates the current branch, and isolates branches into separate worktrees
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-git-branch-manageInstall method: npm · sandbox install ok, web smoke failed (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 |
|---|---|---|
| 1.0.2 | ✗ | · |
| 1.0.1 | · | ✗ |
| v1.0.1 | · | · |
1.0.2npm1 failed2026-10-20
dsh-git-branch-manage
✗dsh 0.2.1-rc.2current2026-10-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-git-branch-manage@1.0.2
ID: dsh-git-branch-4@1.0.2@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
1.0.1npm1 failed2026-10-15
dsh-git-branch-manage
✗dsh 0.2.1-alpha.22026-10-15L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-git-branch-manage@1.0.1
ID: dsh-git-branch-4@1.0.1@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v1.0.1github2026-10-14
https://github.com/GaoHu1997/dsh-git-branch
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-git-branch-4/)`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 — stricter wins → overall medium.
v1.0.2dsh manifest1.0.2npm2026-10-211.0.2same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (3)
- criticalshellExec · shell
lib/git.js:40const result = await exec('git', args, { cwd }); - criticalshellExec · shell
lib/git.js:53const result = await exec('git', args, { cwd }); - warningshellExec · shell
lib/git.js:27execFile(file, args, { cwd: options.cwd, encoding: 'utf8', timeout: 20_000, windowsHide: true, maxBuffer: 4 * 1024 * 1024 }, (error, stdout,
show 1 audit findings
- mediumBranch name reaches git argv without '--', allowing option injection (e.g. force-delete via 'git branch -D')
lib/git.jscreateBranch/renameBranch/deleteBranch/switchBranch assemble git argv from caller-supplied names with no '--' separator and no visible server-side branch-name validation (lib/routes.js is not in the harvested set, and the wire contract calls the name 'verbatim'). A request such as {repoPath, name: '-D', from: 'main'} makes createBranch run 'git branch -D main', i.e. a forced branch deletion that the plugin deliberately refuses to expose (deleteBranch only ever uses the safe '-d'). Similarly '-m'/'-M'/'--list' are taken as options, so refs can be force-renamed or overwritten. The precondition i
One real medium issue: branch names reach git argv without an option terminator, so a crafted request can force-delete branches; the flagged shell/file constructs are otherwise safe.
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-09-29
• Stars: ★ 1 · 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).