Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.3 · 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
A native DSH plugin that rebuilds OpenAI codex-security's discover, verify, report security audit workflow using only DSH models and local JSONL state.
- Discover, verify and report findings, with optional patch/fix re-verification
- Two-stage same-model review dedupes candidates via identity fingerprints
- No embeddings, OpenAI keys, Python or Docker; state kept in local JSONL files
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:id7869/dsh-securityInstall method: GitHub · runtime verified (L5) · verified on dsh 0.2.1-rc.3
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.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| 8ff62e | ✓ | ✓ | ✓ | ✓ | ✓ |
8ff62egithub✓ 11 runtime-verified2026-10-30
https://github.com/id7869/dsh-security
✓dsh 0.2.1-rc.32026-10-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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: github · https://github.com/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-15 · expires: 2026-09-22
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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: github · https://github.com/id7869/dsh-security (version unstated)
ID: dsh-security-2@8ff62e@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
↳ carried from earlier record dsh-security-2@8ff62e@dsh0.2.1-rc.5 (l3-fullscan)
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-security-2/?ref=badge)``[](https://www.dsh.so/artifact/dsh-security-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-security-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-security-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-security-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-security-2/?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 high; dynamic low (authoritative when present) → overall low.
v0.1.0dsh manifest0.1.0git2026-10-300.1.0same versionsuspicious · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalsecretSk · secrets
examples/fixture/src/index.js:12const ADMIN_API_KEY = "sk-live-9f2a1b3c4d5e6f708192a3b4c5d6e7f"; - warningshellExec · shell
examples/fixture/src/index.js:30exec(`ping -c 1 ${host}`, (err, out) => res.send(out));
show 2 audit findings
- lowVulnerable example app ships in the package but is never loaded at runtime
examples/fixture/src/index.js:30The fixture deliberately demonstrates command injection, SQL injection, XSS and path traversal and is included in the published "files" list. It is not referenced by lib/index.js, not exported, and package.json declares no dependencies/scripts, so it cannot execute as part of the plugin; impact is limited to scanners flagging the package and to a developer copying the sample mistakenly.
- lowfix.js inserts args into subagent prompts without the path sanity check used by scan.js
workflow/fix.js:4scan.js/diff.js/track.js reject repo/outputDir/stateDir containing '..' or empty, but fix.js does not; it passes those values into prompts whose subagents may edit source files. Exploitation requires a hostile caller of the workflow and a subagent that ignores its stated write boundaries, so no reachable impact is demonstrated.
Static-scan 'fail' comes from an intentionally vulnerable example app that the plugin never loads; the shipped runtime (lib/index.js) is a benign skill provider.
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-09-15 · activity: Stable
• Repo created: 2026-09-14
• Stars: ★ 2 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/id7869/dsh-security
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-security?
dsh-security 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-security?
Run dsh plugin --profile web add github:id7869/dsh-security 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-10-30 (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.