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
Zero-dependency incident toolkit giving agent hosts one entry point for stuck services, frozen UIs, rollbacks and data loss, plus a hand-off report.
- One entry point for four incident types: stuck, frozen, rollback, data loss
- Read-only by default for safe on-site diagnosis
- Emits a hand-off-ready on-site report
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.
8 samples (roughly every 7 days), 4 of them reconstructed (hollow dots); sampled points, not a daily series
09-28 → 11-02 · 8 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-03 → 11-02 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
10-24 → 11-03 · 11 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
10-24 → 11-04 · 12 points
Installation
dsh plugin --profile web add @kira905/dsh-firstaidInstall method: npm · 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
○ The author declares no dsh version requirement — install is not blocked by version.
| 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 |
|---|---|---|---|---|---|
| 0.1.4 | ○ | · | · | · | · |
| 0.1.3 | · | ○ | ○ | · | · |
| v0.1.3 | · | · | · | ○ | · |
| v0.1.2 | · | · | · | · | · |
| v0.1.1 | · | · | · | · | ○ |
0.1.4npm○ 1 ecosystem plugin2026-11-01
@kira905/dsh-firstaid
○dsh 0.2.1-rc.52026-11-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · @kira905/dsh-firstaid@0.1.4
ID: dsh-firstaid@0.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.
0.1.3npm○ 2 ecosystem plugin2026-10-27
@kira905/dsh-firstaid
○dsh 0.2.1-rc.32026-10-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · @kira905/dsh-firstaid@0.1.3
ID: dsh-firstaid@0.1.3@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-21Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @kira905/dsh-firstaid@0.1.3
ID: dsh-firstaid@0.1.3@dsh0.2.1-rc.2 · profile: l3-fullscan
Issued: 2026-10-21 · expires: 2026-10-28
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.3github○ 1 ecosystem plugin2026-10-18
https://github.com/kira905/dsh-firstaid
○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-firstaid#v0.1.3
ID: dsh-firstaid@v0.1.3@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.2github2026-10-15
https://github.com/kira905/dsh-firstaid
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.1github○ 4 ecosystem plugin2026-10-12
https://github.com/kira905/dsh-firstaid
○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-firstaid#v0.1.1
ID: dsh-firstaid@v0.1.1@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-firstaid#v0.1.1
ID: dsh-firstaid@v0.1.1@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-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/kira905/dsh-firstaid#v0.1.1
ID: dsh-firstaid@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.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/kira905/dsh-firstaid#v0.1.1
ID: dsh-firstaid@v0.1.1@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-firstaid/?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.40.1.4npm2026-11-01v0.1.4version moved onclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (12)
- criticalspawnShell · shell
drill.mjs:295const p = spawnSync(ctx.opt.probe, { shell: true, encoding: 'utf8' }) - warningchildProcess · code-exec
drill.mjs:205const r = spawnSync(process.execPath, [ctx.opt.sandboxCmd, ...args], { encoding: 'utf8', cwd: ctx.point }) - warningchildProcess · code-exec
drill.mjs:271const r = spawnSync(process.execPath, [ctx.restoreScript, ...ctx.opt.restoreArgs], { - warningchildProcess · code-exec
drill.mjs:295const p = spawnSync(ctx.opt.probe, { shell: true, encoding: 'utf8' }) - warningfsWrite · files
drill.mjs:260fs.writeFileSync(t.dst, `${BREAK_MARK} ${new Date().toISOString()}\n`, 'utf8') - warningfsWrite · files
drill.mjs:369fs.writeFileSync(mdPath, md, 'utf8') - warningfsWrite · files
drill.mjs:370fs.writeFileSync(jsonPath, JSON.stringify(json, null, 2), 'utf8') - warningnetIp · network
firstaid.mjs:54const DSH_URL = `http://127.0.0.1:${PORT}/` - warningchildProcess · code-exec
lib/common.mjs:228const r = spawnSync(exePath, ['-NoProfile', '-NonInteractive', '-Command', cmd], { - warningchildProcess · code-exec
lib/common.mjs:245const r = spawnSync('wmic', ['process', 'get', 'ProcessId,Name,CommandLine', '/format:csv'], { - warningchildProcess · code-exec
lib/common.mjs:267const r = spawnSync('tasklist', ['/FO', 'CSV', '/NH'], { encoding: 'utf8', windowsHide: true, maxBuffer: 32 * 1024 * 1024 }) - warningfsWrite · files
lib/common.mjs:445fs.writeFileSync(file, content, 'utf8')
show 3 audit findings
- mediumdrill.mjs runs the --probe string through a shell without quoting
drill.mjs:294The probe text (documented as '验活命令（shell 执行，exit 0 判通过）') is handed to the platform shell verbatim. When drill.mjs is driven by automation/an agent that builds the probe from report text, log tails, tickets or other untrusted content, shell metacharacters (`;`, `&&`, backticks) execute arbitrary commands under the operator's account. Interactive use by a human is only self-inflicted.
- lowDrill executes an arbitrary/auto-detected restore script with node
drill.mjs:270The restore script path comes from --restore or from auto-detection of the single restore-*.mjs inside the rollback point directory; the sandbox path (line 204) does the same for --sandbox-cmd. A rollback point synced from a colleague or produced by an agent is a data directory, so code stored there runs with user privileges. Gated by an explicit --live --yes plus a 3-gate preflight, so it is a user-consented action rather than a hidden backdoor.
- lowLive drill overwrites the real target with DRILL-BROKEN before restoring from a temp snapshot
drill.mjs:259Under --live --yes (and --break-mode remove uses fs.rmSync on the target), the real file is deliberately destroyed and later restored from a copy in an os.tmpdir() directory inside a finally block. If the process is killed, the temp dir is cleaned, or the target is on another volume, the target stays corrupted; recovery then depends on the backup source under the rollback point. Intentional and documented behaviour, but it is genuine destructive capability on arbitrary paths supplied via --target.
Local incident-response CLI with no deps or network egress; the main residual risk is drill.mjs running operator-supplied shell/script strings and destructive live-mode file writes gated only by --yes.
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-22
• Stars: ★ 1 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/kira905/dsh-firstaid
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-firstaid?
@kira905/dsh-firstaid 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-firstaid?
Run dsh plugin --profile web add @kira905/dsh-firstaid 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.