Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
Two DeepSeek Harness plugins: probe-battery tools and an evidence dashboard for archiving results.
- dsh-prior-probe: frozen probe-battery tool bundle
- dsh-evidence-dashboard: archive dashboard
- Meant for DeepSeek Harness integration
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:SuTang-vain/dsh-self-harness-tools#v1.7.0Install method: GitHub · 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.
8 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-05 · 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-24 → 11-05 · 7 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○ Ecosystem plugin
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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v1.7.0 | ○ | ○ | ○ | ○ | ○ |
v1.7.0github○ 16 ecosystem plugin2026-11-14
https://github.com/SuTang-vain/dsh-self-harness-tools
○dsh 0.2.2-rc.3current2026-11-14Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-14 · expires: 2026-11-21
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-06Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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.1-rc.52026-11-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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.1-rc.32026-10-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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.1-rc.22026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-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.1-alpha.42026-10-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
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.1-alpha.22026-10-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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.0-rc.22026-10-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.0-rc.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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.1.7-rc.22026-09-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
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.1.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
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.1.6-alpha.12026-09-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.1.5-rc.22026-09-13Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
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.1.3-alpha.22026-09-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
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.1.3-alpha.12026-09-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
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.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/SuTang-vain/dsh-self-harness-tools#v1.7.0
ID: dsh-self-harness-tools@v1.7.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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.
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-self-harness-tools/?ref=badge)`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.
—v1.7.0git2026-11-14v1.7.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- criticalnewFunction · code-exec
dsh-plugin-kit.ext.cjs:21const lib = new Function('harness', 'web', hostSrc.slice(start, end) + '; return { BATTERIES, matchProbe }')( - criticalnewFunction · code-exec
dsh-plugin-kit/lib/checks.cjs:54new Function(read(ctx.root, file)) - warningchildProcess · code-exec
dsh-plugin-kit/lib/checks.cjs:60const check = spawnSync(process.execPath, ['--check', abs(ctx.root, file)], { encoding: 'utf8' }) - warningchildProcess · code-exec
dsh-plugin-kit/lib/checks.cjs:143const result = spawnSync('npm', args, { cwd: path.join(ctx.root, dir), encoding: 'utf8' }) - warningfsWrite · files
dsh-plugin-kit/lib/genbundle.cjs:77fs.writeFileSync(toAbs, bundle)
show 5 audit findings
- highprior_probe_run reads an arbitrary file's first line as a Bearer token and sends it to a caller-chosen URL
plugins/prior-probe/index.js:171base_url and api_key_file are both model-controlled and neither is validated: no host allowlist, no path restriction. A prompt-injected tool call can point base_url at an attacker endpoint and api_key_file at any readable file (e.g. ~/.aws/credentials, ~/.ssh/id_rsa, .env), whose first line is then POSTed to the attacker as the Authorization header. This is an arbitrary-file-read plus credentialed exfiltration primitive reachable from the model tool surface of the plugin.
- mediumverify CLI executes code supplied by the repository under verification
dsh-plugin-kit/lib/runner.cjs:64run with --root pointed at a third-party plugin repository, the runner require()s and invokes every export of a file taken from that repository, and dsh-plugin-kit.ext.cjs additionally slices a repository source file and evaluates it with new Function (dsh-plugin-kit.ext.cjs:21, fed from plugins/prior-probe/plugin.host.js), handing it a harness stub. The verified artifact therefore runs with the verifier's privileges (filesystem, environment, CI secrets). Precondition: the developer/CI must run the kit against an untrusted repository, which is the tool's normal use case.
- lowparse check compiles a config-named repository file with new Function (compile only)
dsh-plugin-kit/lib/checks.cjs:54The verify config controls both the file path and mode, so an untrusted repository makes the verifier compile arbitrary source inside its own process. new Function only compiles here (the body is not invoked), so there is no immediate execution, but it is the same untrusted-source path that the extension loader turns into real execution, and it can still trigger pathological compile costs.
- lowDashboard route and host half disclose absolute server paths
plugins/evidence-dashboard/index.js:66The unauthenticated exact route /api/dash-data?dataset=catalog returns the absolute data directory of the host filesystem to any web client that can reach the route. plugins/evidence-dashboard/plugin.host.js:16 compounds this by hardcoding a developer home path ('/Users/tangyaoyue/DEV/deepseek_harnees_experiment/opensource/plugins/evidence-dashboard/data') that is tried first on every lookup, leaking the author's local layout and silently preferring a machine-specific directory.
- lowAPI key passed as a tool argument is persisted in the session log
plugins/prior-probe/index.js:156The plugin itself documents that the api_key argument is recorded in this session's log, so callers that follow the simplest path place a live credential in transcript/log storage that is likely shared or retained longer than the secret's lifetime. The alternative (api_key_file) is the path that creates the exfiltration primitive described above.
Developer QA toolkit is mostly benign, but prior-probe's model-reachable prior_probe_run can read any file's first line and send it as a Bearer token to an attacker-chosen URL.
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-16 · activity: Inactive
• Repo created: 2026-08-15
• 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-self-harness-tools?
dsh-self-harness-tools is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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-self-harness-tools?
Run dsh plugin --profile web add github:SuTang-vain/dsh-self-harness-tools#v1.7.0 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-14 (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.