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
Read-only DSH diagnostics for dependency-closure and decoupling checks plus chat image attachment reconciliation.
- Dependency-closure and decoupling checks
- Chat image attachment reconciliation
- Zero dependencies, read-only, reproducible
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.
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); the npm pair from every snapshot.
6 samples (roughly every 1 days), 3 of them reconstructed (hollow dots); sampled points, not a daily series
09-22 → 10-30 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-05 → 10-30 · 3 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:kira905/dsh-diagnostic-tools#v0.1.4Install method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.1-rc.5
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.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| v0.1.4 | ○ | ○ | ○ | ○ | · |
| v0.1.3 | · | · | · | · | · |
| v0.1.2 | · | · | · | · | ○ |
| v0.1.1 | · | · | · | · | · |
v0.1.4github○ 4 ecosystem plugin2026-11-01
https://github.com/kira905/dsh-diagnostic-tools
○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/kira905/dsh-diagnostic-tools#v0.1.4
ID: dsh-diagnostic-tools@v0.1.4@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/kira905/dsh-diagnostic-tools#v0.1.4
ID: dsh-diagnostic-tools@v0.1.4@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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/kira905/dsh-diagnostic-tools#v0.1.4
ID: dsh-diagnostic-tools@v0.1.4@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-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.2.1-alpha.42026-10-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/kira905/dsh-diagnostic-tools#v0.1.4
ID: dsh-diagnostic-tools@v0.1.4@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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.
v0.1.3github2026-10-15
https://github.com/kira905/dsh-diagnostic-tools
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
v0.1.2github○ 3 ecosystem plugin2026-10-12
https://github.com/kira905/dsh-diagnostic-tools
○dsh 0.2.1-alpha.22026-10-12Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/kira905/dsh-diagnostic-tools#v0.1.2
ID: dsh-diagnostic-tools@v0.1.2@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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/kira905/dsh-diagnostic-tools#v0.1.2
ID: dsh-diagnostic-tools@v0.1.2@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.
○prehistory2026-10-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/kira905/dsh-diagnostic-tools#v0.1.2
ID: dsh-diagnostic-tools@v0.1.2@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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.
v0.1.1github○ 2 ecosystem plugin2026-09-30
https://github.com/kira905/dsh-diagnostic-tools
○dsh 0.2.0-rc.12026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/kira905/dsh-diagnostic-tools#v0.1.1
ID: dsh-diagnostic-tools@v0.1.1@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
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-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/kira905/dsh-diagnostic-tools#v0.1.1
ID: dsh-diagnostic-tools@v0.1.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-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.
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-diagnostic-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 medium (authoritative when present) → overall medium.
—v0.1.4git2026-11-01v0.1.4same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningfsWrite · files
attachments/attachments-audit.mjs:114fs.writeFileSync(tmp, JSON.stringify(data), 'utf8') - warningfsWrite · files
attachments/attachments-fetch.mjs:205fs.writeFileSync(tmp, bytes) - warningfsWrite · files
attachments/attachments-fetch.mjs:286fs.writeFileSync(path.join(outDir, 'manifest.json'), JSON.stringify(manifest, null, 2), 'utf8') - warningfsWrite · files
attachments/attachments-fetch.mjs:472fs.writeFileSync(reportPath, JSON.stringify(report, null, 2), 'utf8') - warningfsWrite · files
closure/check-decoupling.mjs:688fs.writeFileSync(args.json, JSON.stringify({ - warningchildProcess · code-exec
closure/repair-closure-links.mjs:90attempts.push(() => { const r = spawnSync('cmd', ['/c', 'rd', full], { windowsHide: true, encoding: 'utf8' }); if (r.status !== 0) throw new - warningfsWrite · files
closure/repair-closure-links.mjs:226fs.writeFileSync(rollbackFile, JSON.stringify({
show 4 audit findings
- mediumAdapter verifier auto-discovered in the scan root is dynamically imported and executed
closure/check-decoupling.mjs:659resolveAdapterVerifier() falls back to `path.join(root ?? DEFAULT_ROOT, 'sync-host-adapter.mjs')`, where DEFAULT_ROOT defaults to cwd/tools or cwd. Running `node check-decoupling.mjs` inside an untrusted checkout that contains tools/sync-host-adapter.mjs executes that file's top-level code (or any file passed via --adapter-verifier / DECOUPLING_ADAPTER_VERIFIER) with the user's privileges, and the loaded module's verifySummary() is then called.
- mediumRollback mode deletes any filesystem path listed in the supplied report JSON
attachments/attachments-fetch.mjs:255`--rollback <report.json>` trusts every `fetched[].target` string and unlinks it without checking that it lies inside <objects-root> or matches a sha256 basename. Because this plugin's premise is moving reports/relay data between machines (reports land in <workspace>/_tmp/attachments-fetch), a crafted or tampered report causes deletion of arbitrary user-writable files when the documented rollback command is run.
- lowRollback restores links using unvalidated paths from the rollback JSON
closure/repair-closure-links.mjs:273rollbackFrom() consumes entries from a JSON file without the linkRoot containment check that planRepairs() applies, so a crafted rollback file can make the tool unlink an existing symlink/junction anywhere on disk and create a new junction at an arbitrary path (if it does not already exist). This only matters when the operator runs `--rollback` on an untrusted manifest.
- lowWindows fallback runs an unquoted `cmd /c rd <path>` built from a discovered link path
closure/repair-closure-links.mjs:90On win32, when unlinkSync/rmdirSync both fail, the link path is passed to cmd.exe unquoted; a directory or link name containing cmd metacharacters (e.g. `&`) inside the link root would be re-parsed by cmd as an additional command. Reachability is narrow (win32 only, both prior removal attempts must throw), so impact is limited to a hardening gap.
Diagnostic CLI suite: mostly read-only checks, but it auto-imports and executes a verifier module found in the scanned directory and deletes paths listed in rollback JSON.
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-11-02 · activity: Active
• Repo created: 2026-09-21
• Stars: ★ 1 · 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).
Frequently asked questions
What is @kira905/dsh-diagnostic-tools?
@kira905/dsh-diagnostic-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 @kira905/dsh-diagnostic-tools?
Run dsh plugin --profile web add github:kira905/dsh-diagnostic-tools#v0.1.4 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-02 (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.