Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
DSH security patrolling plugin combining SSH-based remote scanning with Semgrep code analysis and reporting.
- Transforms pentest steps into proactive defense patrols
- Uses Semgrep for static vulnerability scanning
- Executes remote security checks and generates reports via SSH
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-dolphin-securityInstall 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
Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages. raw ranges
^0.1.5-rc.1 || ^0.2.0-rc.2 ×1
✓ Running dsh 0.2.1-rc.2 is within the declared range — install is not blocked by version.
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.3.1 | ✓ | · | · | · | · |
| 0.3.0 | · | ✓ | · | · | · |
| 0.2.6 | · | · | ✓ | ✓ | ✓ |
| 0.2.5 | · | · | · | · | · |
| 0.2.4 | · | · | · | · | · |
0.3.1npm✓ 1 runtime-verified2026-10-21
dsh-dolphin-security
✓dsh 0.2.1-rc.2current2026-10-21L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-dolphin-security@0.3.1
ID: dsh-dolphin-security@0.3.1@dsh0.2.1-rc.2 · profile: l3-fullscan
Issued: 2026-10-21 · expires: 2026-10-28
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.
0.3.0npm✓ 1 runtime-verified2026-10-18
dsh-dolphin-security
✓dsh 0.2.1-alpha.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-dolphin-security@0.3.0
ID: dsh-dolphin-security@0.3.0@dsh0.2.1-alpha.4 · 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.
0.2.6npm✓ 4 runtime-verified2026-10-12
dsh-dolphin-security
✓dsh 0.2.1-alpha.22026-10-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-dolphin-security@0.2.6
ID: dsh-dolphin-security@0.2.6@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: npm · dsh-dolphin-security@0.2.6
ID: dsh-dolphin-security@0.2.6@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.2.0-rc.12026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-dolphin-security@0.2.6
ID: dsh-dolphin-security@0.2.6@dsh0.2.0-rc.1 · profile: l4-sandbox
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.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-dolphin-security@0.2.6
ID: dsh-dolphin-security@0.2.6@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.
0.2.5npm✓ 5 runtime-verified2026-09-26
dsh-dolphin-security
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-dolphin-security@0.2.5
ID: dsh-dolphin-security@0.2.5@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-24L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-dolphin-security@0.2.5
ID: dsh-dolphin-security@0.2.5@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
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-dolphin-security@0.2.5
ID: dsh-dolphin-security@0.2.5@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-dolphin-security@0.2.5
ID: dsh-dolphin-security@0.2.5@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-dolphin-security@0.2.5
ID: dsh-dolphin-security@0.2.5@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.
0.2.4npm✓ 1 runtime-verified2026-09-13
dsh-dolphin-security
✓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-dolphin-security@0.2.4
ID: dsh-dolphin-security@0.2.4@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.
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-dolphin-security/)``[](https://www.dsh.so/artifact/dsh-dolphin-security/)``[](https://www.dsh.so/artifact/dsh-dolphin-security/)``[](https://www.dsh.so/artifact/dsh-dolphin-security/)``[](https://www.dsh.so/artifact/dsh-dolphin-security/)``[](https://www.dsh.so/artifact/dsh-dolphin-security/)``[](https://www.dsh.so/artifact/dsh-dolphin-security/)`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.
v0.2.0dsh manifestv0.2.0git2026-10-21v0.3.1version moved onclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (8)
- criticalosSystem · shell
dolphin-core.js:236message: "Found user-controlled data in os.system() call. This could be vulnerable to command injection.", - criticalosSystem · shell
dolphin-core.js:244lines: ' os.system("rm -rf " + user_input)', - criticaldestructiveRm · destructive
dolphin-patrol.js:605const c4 = buildRemoteScanCommand('/x', "p/foo'; rm -rf /tmp/x; #") - criticaldestructiveRm · destructive
dolphin-patrol.js:608check('恶意规则集被转义(; 与 rm 被单引号包裹)', c4 === "semgrep scan --config 'p/foo'\\''; rm -rf /tmp/x; #' /x --json", c4) - criticalshellExec · shell
dolphin-ssh-core.js:1068async exec(alias, command, timeoutMs, attempts) { - criticalsecretPem · secrets
dolphin-ssh-core.js:1160writeFileSync(keyFile, '-----BEGIN OPENSSH PRIVATE KEY-----\n(self-test fixture)\n-----END OPENSSH PRIVATE KEY-----\n') - warningchildProcess · code-exec
dolphin-patrol.js:192const r = spawnSync(bin, args, { encoding: 'utf8' }) - warningshellExec · shell
dsh-code-scan/lib/scanner.js:35execFile(
show 2 audit findings
- mediumtargetDir is passed to semgrep as an unvalidated argv element (argument injection)
dsh-code-scan/lib/scanner.js:29dolphin_scan / dolphin_patrol accept targetDir directly from the agent and never check that it is a path. Because semgrep receives it as a bare argv element (after 'scan --json --config <rc>'), a value such as '--output=/home/user/.bashrc' or '--config=/etc/passwd' is interpreted as a semgrep flag: any writable file can be overwritten with scan output, and arbitrary files can be pulled in as rule configs. The local path (execFile, no shell) is directly reachable; the remote path applies the same pass-through because shellQuote's whitelist permits a leading '-', although the earlier `test -d` p
- lowSSH passwords / key passphrases persisted in plaintext in ~/.dolphin/dolphin-ssh-hosts.json
dolphin-ssh-core.jsHostStore.create/update keep password and passphrase authentication material as cleartext JSON, written by save() with mode 0o600 into a 0700 directory. That limits exposure to the same OS account, but any other process running as that user, a profile backup/snapshot, or a synced home directory can read the credentials. The API surface is otherwise careful (summarize() redacts secrets and the self-test asserts this).
Semgrep/SSH scanning is legitimate and sudo/rm -rf/quoting guards hold; residual risk is unvalidated targetDir argument injection into semgrep plus plaintext SSH secrets.
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-19 · activity: Active
• Repo created: 2026-09-01
• Stars: ★ 0 · 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).
