基于 DeepSeek Harness 的多 Agent PTES 渗透测试编排插件,支持自动化侦察、漏洞分析、验证与报告,使用 Docker/Kali 隔离工具箱 | Multi-agent PTES penetration testing plugin for DeepSeek Harness with automated recon, vulnerability analysis, validation, reporting, and Docker/Kali toolbox
Install verification: runtime test inconclusive (L5 unknown) · tested on dsh 0.2.2-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
PTES-inspired penetration testing orchestration plugin for DeepSeek Harness with engagement management, subagents, approvals, and reporting.
- Orchestrates PTES seven-phase pentest workflows with subagents
- Enforces approvals and capability controls via Tool Broker
- Persists artifacts/evidence/findings and generates report.md
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-pentesterInstall method: npm · runtime test inconclusive (L5 unknown)
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, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
current (registry 2026-11-19) · 9 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-03 · 9 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
09-28 → 11-03 · 8 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-07 → 11-17 · 65 points
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
09-07 → 11-17 · 65 points
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 a single engines.dsh range (decides alone; peerDependencies is not consulted). raw ranges
>=0.2.0-rc.1 <0.3.0
✓ Running dsh 0.2.2-rc.5 is within the declared range — install is not blocked by version.
Deciding channel: since 0.2.1-alpha.4 DSH judges by engines.dsh when declared — peerDependencies is then not consulted.
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin \ dsh | dsh 0.2.2-rc.5 current | dsh 0.2.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 |
|---|---|---|---|---|---|
| 6.5.0 | ○ | ○ | ✗ | ✗ | ✗ |
| v6.5.0 | · | · | · | · | · |
| v6.4.0 | · | · | · | · | · |
| 6.3.0 | · | · | · | · | · |
| v6.3.0 | · | · | · | · | · |
6.5.0npm5 failed2026-11-19
dsh-pentester
○dsh 0.2.2-rc.5current2026-11-19not tested
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.5
- • Plugin artifact: npm · dsh-pentester@6.5.0
ID: dsh-pentester@6.5.0@dsh0.2.2-rc.5 · profile: l4-sandbox
Issued: 2026-11-19 · expires: 2026-11-26
View checks & evidence
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.
○dsh 0.2.2-rc.32026-11-19not tested
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-pentester@6.5.0
ID: dsh-pentester@6.5.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-19 · expires: 2026-11-26
View checks & evidence
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.
✗dsh 0.2.2-rc.12026-11-04L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-pentester@6.5.0
ID: dsh-pentester@6.5.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
View checks & evidence
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-30L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-pentester@6.5.0
ID: dsh-pentester@6.5.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-pentester@6.5.0
ID: dsh-pentester@6.5.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
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-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-pentester@6.5.0
ID: dsh-pentester@6.5.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-pentester@6.5.0
ID: dsh-pentester@6.5.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
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.
v6.5.0github2026-10-14
https://github.com/fb0sh/dsh-pentester
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v6.4.0github2026-10-13
https://github.com/fb0sh/dsh-pentester
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
6.3.0npm1 failed2026-10-13
dsh-pentester
✗dsh 0.2.1-alpha.22026-10-13L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-pentester@6.3.0
ID: dsh-pentester@6.3.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-13 · expires: 2026-10-20
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v6.3.0github2026-10-10
https://github.com/fb0sh/dsh-pentester
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-pentester/?ref=badge)``[](https://www.dsh.so/artifact/dsh-pentester/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-pentester/?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 high (authoritative when present) → overall high.
v6.5.0dsh manifest6.5.0npm2026-11-196.5.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (5)
- criticalshellExec · shell
lib/runtime-B0U-zaML.js:551async exec(context, input) { - criticalshellExec · shell
lib/runtime-BB0bKz9z.js:561async exec(context, input) { - criticalshellExec · shell
lib/runtime-CkIju_Cz.js:426async exec(context, input) { - criticalshellExec · shell
lib/runtime-D5tI6R3t.js:561async exec(context, input) { - criticalshellExec · shell
lib/runtime-DcRIHRYS.js:426async exec(context, input) {
show 2 audit findings
- highExisting exec-guard.sh regular file is trusted as-is, so the supervised Worker can replace the host-owned guard
lib/runtime-D5tI6R3t.jsThe guard that implements the host's supervision (setsid/pidfile, process-group TERM->KILL on timeout/cancel) is written only when the path does not already exist as a regular file, then merely chmod 700'd. It lives at <workspaceRoot>/<instanceId>/.control/exec-guard.sh and every supervised command is launched with `sh <guardPath> <token> --cwd <cwd> <argv...>`, i.e. the guard is re-read from disk on every exec and never integrity-checked. The Worker executes as the same SSH user with unrestricted argv (it can run `sh -c '...'`), so it can atomically rename a replacement script over that path;
- mediumRemote SFTP entry names are joined into local paths without path-traversal validation during workspace pull
lib/runtime-D5tI6R3t.jsdownloadTree builds the local destination from the SFTP listing returned by the remote host and only bounds its length; entry names containing `..`/absolute components (a hostile or compromised SFTP server can return arbitrary names, and ssh2 passes them through verbatim) make join(localDir, rel) resolve outside the Delegation workspace, so pullWorkspace can create/overwrite arbitrary host files (e.g. shells rc files or plugin JS) and the same names also enter the `seen` set used by deleteMissingFiles. Requires control of the configured SSH endpoint, but that upgrades a 'remote host I connecte
SSH runtime quotes argv and supervises commands, but an already-existing exec-guard.sh is trusted and the supervised Worker can overwrite it, stealing the sudo password; workspace pull also lacks path-traversal checks.
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-28 · activity: Active
• Repo created: 2026-08-19
• Stars: ★ 104 · Forks: 23
• Health: Active — committed within last 30 days
Source
GitHub: github.com/fb0sh/dsh-pentester
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-pentester?
dsh-pentester 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-pentester?
Run dsh plugin --profile web add dsh-pentester in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed yet.
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-19 (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.
