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
Graceful restart/shutdown guardian for DeepSeek Harness; waits for rounds, auto-resumes sessions, rolls back failures.
- Waits for agent rounds to finish before restart
- Auto-wakes sessions and steers agent to continue
- Automatic rollback on spawn failure from snapshots
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:msilita/dsh-graceful-restart#v1.1.0Install 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.
10 samples (roughly every 7 days), 4 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-14 · 10 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-14 · 9 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
^0.1.0-rc.6 ×1
✗ Running dsh 0.2.2-rc.5 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-graceful-restart@1.1.0 0.2.2-rc.5 (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.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| v1.1.0 | ✗ | ✗ | ✗ | ✗ | ✗ |
v1.1.0github13 failed2026-11-14
https://github.com/msilita/dsh-graceful-restart
✗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/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@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-28L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-28 · expires: 2026-11-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.
✗dsh 0.2.1-rc.22026-10-20L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
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/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@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-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@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.6-alpha.22026-09-21L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-21 · expires: 2026-09-28
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-17L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@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/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@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/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@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/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@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.
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/msilita/dsh-graceful-restart#v1.1.0
ID: dsh-graceful-restart@v1.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-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-graceful-restart/?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.
v1.1.0dsh manifestv1.1.0git2026-11-19v1.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (10)
- warningchildProcess · code-exec
lib/index.js:383const child = spawn(idx.execPath, argv, { - warningchildProcess · code-exec
lib/index.js:418const child = spawn(process.execPath, [ - warningchildProcess · code-exec
lib/index.js:968return spawnSync(process.execPath, [process.argv[1], 'plugin', '--profile', profile, ...args], { - warningnetIp · network
lib/index.js:721const res = await fetch('http://127.0.0.1:' + TARGET_PORT + '/plugins/' + pkg + '/client.js', { - warningnetIp · network
lib/index.js:788const base = 'http://127.0.0.1:' + TARGET_PORT - warningfsWrite · files
lib/index.js:247fs.writeFileSync(FILE.snapshot(), JSON.stringify(payload, null, 2) + '\n', 'utf8') - warningfsWrite · files
lib/index.js:252try { fs.appendFileSync(FILE.log(), `${new Date().toISOString()} ${msg}\n`, 'utf8') } catch { /* best-effort */ } - warningfsWrite · files
lib/index.js:264try { fs.writeFileSync(stderrFile(), '', 'utf8') } catch { /* best-effort */ } - warningchildProcess · code-exec
lib/launcher.cjs:55current = spawn(process.execPath, [binJs, ...dshArgs], { - warningfsWrite · files
lib/launcher.cjs:27try { fs.appendFileSync(logFile, new Date().toISOString() + ' launcher: ' + msg + '\n', 'utf8') } catch {}
show 3 audit findings
- mediumUnauthenticated loopback endpoints let any web page force a restart/rollback (no origin or CSRF check)
lib/index.js:1496The handler only checks the HTTP method; it performs no Origin/Sec-Fetch-Site check and no token check. A plain cross-site form/fetch (mode:'no-cors', text/plain body) from any page the user visits can POST to http://127.0.0.1:3080/plugins/dsh-graceful-restart/page-failed (JSON parse failure is swallowed, so a dummy body works). The host then forwards refresh-failed to the wrapper, which kills the live dsh process and walks the snapshot rollback path: it runs `node <bin.js> plugin remove <pkg>` / `plugin add <pkg@spec>` for the plugins that differ from the previous baseline and may end with no
- lowDetached restart executor trusts execPath/argv read from a mutable file in $DSH_HOME
lib/index.js:383spawnExecutor() first writes $DSH_HOME/dsh-graceful-restart-executor.cjs and runs it detached with the full environment; that script then reads $DSH_HOME/dsh-process.json and spawns whatever executable and arguments it contains. Anything able to write either file (another plugin, a script, a restored backup, a shared/network $DSH_HOME) can therefore get code executed as the user at the next restart, and the executed .cjs itself is a mutable on-disk artifact. No privilege boundary is crossed (same user), hence low, but it is a persistence/hijack primitive and an unnecessary trust of on-disk dat
- lowPrevious-generation stderr is injected verbatim into the agent as plugin-form instructions
lib/index.js:302formatIncidents() copies the raw captured boot stderr of the failed generation (output of any plugin, install script or child process) into the wake text, and apply()/tryResumeSessions() steers it to the agent as a user message whose source is { kind: 'plugin', plugin: name, form: 'instructions' }. Text produced by an untrusted plugin or npm postinstall during a failed startup therefore reaches the model tagged as plugin instructions, an indirect prompt-injection path that can ride a self-triggered restart. Preconditions (a wake restart plus a failing generation) keep this low.
Functional restart/guard plugin, but its localhost HTTP endpoints accept state-changing POSTs with no origin/auth check, so any web page can force a restart and plugin rollback.
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-17 · 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-graceful-restart?
dsh-graceful-restart 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-graceful-restart?
Run dsh plugin --profile web add github:msilita/dsh-graceful-restart#v1.1.0 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-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.
