Install verification: runtime verified (L5) · tested on dsh 0.2.2-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
Static analyzer scanning DSH plugins for declared sensitive service capabilities without execution.
- Zero-execution static analysis
- Detects sensitive service references
- Targets DSH cordis plugins
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:heming-gmh/dsh-capcheckInstall method: GitHub · runtime verified (L5) · verified on dsh 0.2.2-rc.3
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.
8 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-13 · 8 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-23 → 11-13 · 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
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
Only 0 points (< 3): no chart yet
no data yet
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
* ×1
✓ Running dsh 0.2.2-rc.5 is within the declared range — install is not blocked by version.
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin \ dsh | dsh 0.2.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| b2aa2b | ✓ | ○ | · | · | · |
| 690049 | · | ✓ | ✓ | ✓ | ✓ |
b2aa2bgithub✓ 1 runtime-verified2026-11-14
https://github.com/heming-gmh/dsh-capcheck
✓dsh 0.2.2-rc.32026-11-14L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/heming-gmh/dsh-capcheck#b2aa2b88c77d2929a3db8c89cc16817f8c639e48
ID: dsh-capcheck@b2aa2b88c77d2929a3db8c89cc16817f8c639e48@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-14 · expires: 2026-11-21
View checks & evidence
active in loader tree (206 entries)
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-13not tested
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/heming-gmh/dsh-capcheck#b2aa2b88c77d2929a3db8c89cc16817f8c639e48
ID: dsh-capcheck@b2aa2b88c77d2929a3db8c89cc16817f8c639e48@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-13 · expires: 2026-11-20
View checks & evidence
inventory probe failed (rpc-error) — inconclusive, not a plugin verdict (reinterpreted 2026-11-17)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
690049github✓ 17 runtime-verified◐ 1 testing2026-11-14
https://github.com/heming-gmh/dsh-capcheck
✓dsh 0.2.2-rc.12026-11-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-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.
✓dsh 0.2.1-rc.52026-10-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
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/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@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/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-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.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/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@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/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@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/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@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.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@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: github · https://github.com/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@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/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@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-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@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-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
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/heming-gmh/dsh-capcheck#690049
ID: dsh-capcheck@690049@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/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@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.
◐dsh 0.1.1-rc.22026-08-28L4 · testing (install passed, runtime untested)
- • Node.js: v24.14.0
- • DSH: 0.1.1-rc.2
- • Plugin artifact: github · https://github.com/heming-gmh/dsh-capcheck#690049
ID: dsh-capcheck@690049@dsh0.1.1-rc.2 · profile: l3-fullscan
Issued: 2026-08-28 · expires: 2026-09-04
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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/heming-gmh/dsh-capcheck (version unstated)
ID: dsh-capcheck@690049@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-capcheck/?ref=badge)``[](https://www.dsh.so/artifact/dsh-capcheck/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-capcheck/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-capcheck/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-capcheck/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-capcheck/?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.
v0.1.0dsh manifest0.1.0git2026-11-190.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (4)
- warningshellExec · shell
src/scan-npm.js:13execFileSync('npm', ['pack', specifier, '--pack-destination', workDir, '--silent'], { encoding: 'utf8', timeout: 30000 }) - warningshellExec · shell
src/scan-npm.js:16execFileSync('tar', ['-xzf', tarball, '-C', workDir], { cwd: workDir }) - warningshellExec · shell
src/scan-remote.js:7const out = execFileSync('gh', ['api', pathSpec], { encoding: 'utf8', maxBuffer: 1024 * 1024 * 20 }) - warningshellExec · shell
src/scan-remote.js:18const out = execFileSync('gh', ['api', 'repos/' + owner + '/' + repo + '/contents/' + filePath, '--jq', '.content'], { encoding: 'utf8', max
show 4 audit findings
- highUnvalidated npm specifier passed to `npm pack`, which runs prepack/prepare lifecycle scripts for git/folder specs
src/scan-npm.js:13The file header claims 'no install, no lifecycle scripts executed', but `npm pack <spec>` does run `prepack`/`prepare` when the specifier resolves to a local folder or a git/URL dependency (pacote clones and builds before packing). The tool's whole purpose is to inspect untrusted packages and the `target` string is attacker-influenceable, so a spec like 'github:attacker/repo' or a dropped directory yields arbitrary code execution in the DSH host process during a scan that is advertised as never-executed.
- mediumSpecifier is not validated, allowing option injection into the npm CLI
src/scan-npm.js:13execFileSync avoids a shell, but a specifier beginning with '-' is still parsed by npm as a flag (e.g. `--registry=<attacker>`, `--userconfig=<path>`), changing where and how the package is fetched/extracted, and interacting with the lifecycle-script issue above (e.g. enabling script execution paths).
- lowUntrusted tarball extracted with tar without entry-path validation
src/scan-npm.js:16The tarball comes from the registry/attacker-controlled source and its entries are never inspected. GNU tar rejects `..` members, but implementations that do not (or symlink/hardlink entries chained with later writes) could write outside the mkdtemp workdir. Impact is limited by the temporary-directory choice, hence low.
- lowEntry path from scanned package.json is joined without containment check
src/scan-package.js:55`main`/`exports` from an untrusted package.json can be `../../../../etc/passwd`, so the tool (and any agent invoking it with kind:'local') can make the process read files outside the target directory. Exposure is limited because file contents are never returned - only extracted capability names and line numbers - so this is a hardening gap rather than a disclosure channel.
Static 'never-executed' scanner is reachable via a DSH tool that spawns 'npm pack' and 'tar' on unvalidated specifiers, so untrusted git/folder specs can run lifecycle scripts (code execution).
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-08-19 · activity: Inactive
• Repo created: 2026-08-19
• Stars: ★ 0 · Forks: 0
• Health: Inactive — no commit in 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-capcheck?
dsh-capcheck 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-capcheck?
Run dsh plugin --profile web add github:heming-gmh/dsh-capcheck 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-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.
