Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Opt-in detached watchdog for the DSH Web process, providing snapshot-checked repair and explicit patch restoration.
- Detached watchdog for DSH Web process
- Snapshot-checked repair mechanism
- Explicit patch restoration
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:xiaohj233/dsh-keepalive#v0.2.14Install method: GitHub · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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.
9 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-03 · 9 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-28 → 11-03 · 8 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 4 @deepseek-ai/dsh-* packages. raw ranges
0.1.0-rc.6 ×4
✗ Running dsh 0.2.2-rc.3 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-keepalive@0.2.14 0.2.2-rc.3 (the exemption lives in the local profile; this site does not assume one)
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.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.2.14 | ✗ | ✗ | ✗ | ✗ | ✗ |
| v0.2.12 | · | · | · | · | · |
v0.2.14github11 failed2026-11-14
https://github.com/xiaohj233/dsh-keepalive
✗dsh 0.2.1-rc.52026-10-30L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.14
ID: dsh-keepalive@v0.2.14@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
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.2.1-rc.32026-10-26L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.14
ID: dsh-keepalive@v0.2.14@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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.2.1-rc.22026-10-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.14
ID: dsh-keepalive@v0.2.14@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
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-15L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.14
ID: dsh-keepalive@v0.2.14@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
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-12L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.14
ID: dsh-keepalive@v0.2.14@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
View checks & evidence
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-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.14
ID: dsh-keepalive@v0.2.14@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.14
ID: dsh-keepalive@v0.2.14@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.14
ID: dsh-keepalive@v0.2.14@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.14
ID: dsh-keepalive@v0.2.14@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
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-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.14
ID: dsh-keepalive@v0.2.14@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-09-30L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.14
ID: dsh-keepalive@v0.2.14@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.2.12github4 failed2026-09-11
https://github.com/xiaohj233/dsh-keepalive
✗dsh 0.1.5-rc.22026-09-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.12
ID: dsh-keepalive@v0.2.12@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
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-08L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.12
ID: dsh-keepalive@v0.2.12@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.12
ID: dsh-keepalive@v0.2.12@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/xiaohj233/dsh-keepalive#v0.2.12
ID: dsh-keepalive@v0.2.12@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
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-keepalive/?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.2.14dsh manifestv0.2.14git2026-11-17v0.2.14same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningchildProcess · code-exec
lib/installed-patches.mjs:133const res = spawnSync(process.execPath, ["--check", file], { - warningchildProcess · code-exec
restarter.mjs:49const child = spawn(process.execPath, args, { - warningchildProcess · code-exec
watchdog.mjs:166const res = spawnSync("ss", ["-tlnp"], { encoding: "utf8", timeout: 8000 }); - warningchildProcess · code-exec
watchdog.mjs:182const res = spawnSync("netstat", ["-ano"], { encoding: "utf8", timeout: 8000, windowsHide: true }); - warningchildProcess · code-exec
watchdog.mjs:202spawnSync("taskkill", ["/PID", String(pid), "/T", "/F"], { timeout: 8000, windowsHide: true });
show 4 audit findings
- mediumUntrusted log/report text is embedded verbatim in the prompt of an LLM repair agent running with approval=never
watchdog.mjs:617`pf` comes from `state.pluginFailure`, which the host writes from the browser POST to /api/keepalive/report-plugin-failure, and the launch-failure variant additionally embeds the entire raw web log (attemptOutput) — all concatenated into the task string passed to `node <bin> --profile headless` (watchdog.mjs:397). That agent is configured with `sandbox: workspace-write` and `approval: never` (lib/llm-config.mjs:180) and inherits process.env. Its cwd/workspace root is the common parent of every link: dev checkout and `repairWorkspaceRoot()` may return a drive root (watchdog.mjs:466), so injecte
- lowWatchdog silently rewrites the source of two @deepseek-ai packages on every start, including untested versions
watchdog.mjs:708With the default `strict: false`, lib/installed-patches.mjs patches any installed version whose anchor text matches uniquely, not only the pinned 0.1.0-rc.6, editing node_modules/@deepseek-ai/dsh-host-apiproxy/lib/index.js and dsh-subprocess-local/lib/index.js. The patch bodies are benign and the guards are real (unique-anchor check, atomic temp+rename, node --check with byte rollback, explicit restore command), so the residual risk is silently modifying/corrupting an untested framework install at boot rather than malicious tampering.
- lowUser credential file is copied into a kept-on-disk repair runtime dir and deleted only best-effort
watchdog.mjs:352The temporary repair home `$DSH_HOME/keepalive-repair-runtime/<attemptId>` is deliberately kept for post-mortem diagnostics; only the credential copy is removed (watchdog.mjs:441) inside a try/catch whose failure is swallowed, so a failed unlink leaves plaintext credentials on disk indefinitely.
- lowDiagnostic script interpolates $DSH_HOME into a `node -e` program string
bin/diagnose-disconnect.sh:44A DSH_HOME containing a single quote breaks out of the require() string and injects JavaScript into the node process. This is a manually run diagnostic (not loaded by the runtime) and the operator controls DSH_HOME, so impact is limited to self-inflicted code execution or garbled output.
Opt-in DSH Web watchdog that relaunches the host, rewrites two framework packages at boot and can drive an LLM repair agent; one medium prompt-injection/write-risk plus minor hygiene gaps.
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-29 · activity: Stable
• Repo created: 2026-08-14
• Stars: ★ 2 · Forks: 0
• Health: Stable — committed within 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-keepalive?
dsh-keepalive 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-keepalive?
Run dsh plugin --profile web add github:xiaohj233/dsh-keepalive#v0.2.14 in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run yet.
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-17 (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.
