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
A DSH plugin bundle whose Git manager adds a sidebar Git panel to DSH Web for branches, staging, commits, push/pull, AI commit messages and diffs.
- Sidebar Git panel follows the current session's cwd, switching repos on session switch
- Branch switching, stage/commit, push/pull plus AI-generated commit messages
- Commit graph and diff viewer, backed by 32 unit tests and 27 RPC smoke tests
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:caozeal/dsh-pluginsInstall 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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.1-rc.2 current |
|---|---|
| 57f968 | ○ |
| 196c91 | · |
57f968github○ 1 ecosystem plugin2026-10-22
https://github.com/caozeal/dsh-plugins
○dsh 0.2.1-rc.2current2026-10-22Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/caozeal/dsh-plugins (version unstated)
ID: dsh-plugins-165@57f968@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-22 · expires: 2026-10-29
View checks & evidence
not in scope for web smoke; see prior standard-profile records
not in scope for web smoke; see prior standard-profile records
↳ carried from earlier record dsh-plugins-165@196c91@dsh0.2.1-rc.2 (l3-fullscan)
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.
196c91local2026-10-22
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-plugins-165/)`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 high — stricter wins → overall high.
—9854fda437degit2026-10-229854fda437desame versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalshellExec · shell
git-manager/index.js:51return async function exec(argv, options = {}) { - criticalshellExec · shell
git-manager/src/operations.js:111const result = await exec(argv, { cwd, signal, timeoutMs })
show 4 audit findings
- highdiff op passes caller-controlled path to `git diff --no-index`, enabling arbitrary file read
git-manager/src/operations.js:268`params.path` is only prefixed with `./` when it starts with `-`; absolute paths and `../` traversal are accepted, and `git diff --no-index` ignores repository boundaries. A caller of the authenticated route (e.g. a same-origin script from another plugin bundle) can request `{op:'diff', cwd:'/any/repo', mode:'untracked', path:'/home/user/.ssh/id_rsa'}` and receives up to 400k chars of the file content in `raw`.
- medium`cwd` is unrestricted: any authenticated caller can run git write/network ops on any repository on the host
git-manager/src/operations.js:41`assertCwd` only requires an absolute path; nothing ties `cwd` to the active session workspace. Every operation (`stage`, `commit`, `push`, `pull`, `fetch`) then runs in that repository using the host's git identity and credential helper, so a caller can modify and push to repositories the user never exposed to this panel.
- lowRef validation allows leading `-`, so branch names can be interpreted as git options
git-manager/src/operations.js:35`assertRef` accepts values such as `-f`; it is then passed as `['checkout', name]`, i.e. `git checkout -f`, which silently discards local modifications. Other option-like values are rejected by git itself, so impact is limited to destructive flags inside the target repository.
- low`remote.origin.url` may contain embedded credentials and is echoed back to every caller
git-manager/src/operations.js:180Repositories configured with `https://user:token@host/...` return that URL verbatim in `snapshot.repo.remoteUrl`, so any same-origin script that can reach the route can harvest tokens stored in git config.
Authenticated git RPC allows an arbitrary file read via `git diff --no-index` in the diff op and lets any caller run git read/write/push operations on any absolute path.
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-22 · activity: Active
• Repo created: 2026-10-22
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/caozeal/dsh-plugins
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).