Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Installs a DSH agent preset that maps bash calls to Git for Windows' MSYS bash, enabling minimal mode on Windows.
- Maps DSH bash calls to Git Bash (MSYS)
- Enables minimal mode on Windows
- One-click preset installation
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.
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); the npm pair from every snapshot.
current (registry 2026-11-12) · 8 samples (roughly every 7 days), 3 of them reconstructed (hollow dots); sampled points, not a daily series
09-21 → 11-09 · 8 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-06 → 11-09 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:liceses/dsh-gitbash-presetInstall method: GitHub · 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin ＼ dsh | dsh 0.2.2-rc.1 current | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 |
|---|---|---|---|---|---|
| fc475f | · | · | · | · | · |
| bd3c15 | ✓ | ✓ | ✓ | ✓ | ✓ |
fc475fgithub2026-08-28
https://github.com/liceses/dsh-gitbash-preset
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
bd3c15github✓ 16 runtime-verified2026-11-05
https://github.com/liceses/dsh-gitbash-preset
✓dsh 0.2.2-rc.1current2026-11-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-12
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-rc.52026-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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-rc.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-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.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-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.
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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.12026-09-24not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
This level was not executed in this scan.
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: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@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: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@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: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@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: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@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.
✓dsh 0.1.3-alpha.12026-09-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
active in loader tree (151 entries)
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-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset#bd3c15
ID: dsh-gitbash-preset@bd3c15@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
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.2-alpha.12026-09-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dsh0.1.2-alpha.1 · profile: l3-fullscan
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
active in loader tree (149 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/liceses/dsh-gitbash-preset (version unstated)
ID: dsh-gitbash-preset@bd3c15@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
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.
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-gitbash-preset/?ref=badge)``[](https://www.dsh.so/artifact/dsh-gitbash-preset/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-gitbash-preset/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-gitbash-preset/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-gitbash-preset/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-gitbash-preset/?ref=badge-install)`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.3dsh manifest0.1.3git2026-11-120.1.3same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (3)
- criticalmanifest-bare-fs · sandbox
agent-presets/minimal-gitbash/agent.cordis.ymlMutating filesystem tool shares a bare fs-local backend - warningchildProcess · code-exec
agent-presets/minimal-gitbash/gitbash-executor.mjs:215return subprocess.spawn(spawnSpec( - warningmanifest-shell-unfenced · sandbox
agent-presets/minimal-gitbash/agent.cordis.ymlShell tool without a sandbox runner or policy in realm
show 3 audit findings
- mediumPreset only runs shell commands unsandboxed and its error text coaches the agent to request danger-full-access
agent-presets/minimal-gitbash/gitbash-executor.mjs:192The executor rejects every mode except `danger-full-access` (line 256: `if (mode !== undefined && mode !== 'danger-full-access')`), so this preset can never run a confined command; and when blocked it emits a message telling the model to re-issue the command with a one-shot sandbox escalation. An agent that follows the message trains itself to escalate to unrestricted host execution, and the getter at line 227 advertises `sandboxMode` so the bash tool offers that escalation path.
- lowPreset config files installed on boot are not part of the audited source set
lib/index.js:26`agent.cordis.yml` and `preset.yml` are copied into the user preset root (line 67) and are later loaded by DSH as the agent's persona/tool configuration, but they were not included in the harvested source, so their contents (system prompt, tool grants, any embedded commands) could not be verified. Any unreviewed instructions in them would execute in the agent's context.
- lowShell executable is resolved from GIT_BASH and PATH without any integrity check
agent-presets/minimal-gitbash/gitbash-executor.mjs:85`detectShellPath` returns the first existing candidate from `env.GIT_BASH` and then from every directory in `PATH` (`candidates.push(`${dir}\\bash.exe`)`, line 95). Anything that can drop a `bash.exe` in a user-writable PATH directory (and no standard Git install exists) becomes the interpreter for every agent shell command. Requires pre-existing local write access, so the reachable impact is limited.
Refutes the scanner's critical: `bash -c` is the plugin's intended shell provider; residual risk is a preset that only runs with danger-full-access and coaches the agent to escalate.
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-10-07 · activity: Stable
• Repo created: 2026-08-15
• Stars: ★ 128 · Forks: 2
• 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-gitbash-preset?
dsh-gitbash-preset is a DeepSeek Harness (dsh) plugin listed on dsh.so — an independent community registry that indexes public source repositories and publishes automated security-scan and install-verification results for each entry.
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-gitbash-preset?
Run dsh plugin --profile web add github:liceses/dsh-gitbash-preset in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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-12 (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.