The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.

dsh-host-update avatar

dsh-host-update

DSH宿主本体自动更新插件 —— 侧边栏独立入口,检测 @deepseek-ai/dsh 更新、一键静默更新并重启,并对当前 profile 的插件做兼容性诊断

PluginAutomationDesktopInterface & Layout
Verification
L4 · Install tested
stale
Risk
Out of scope
Health
Inactive
Trust
Silver

Install verification: sandbox install passed (L4) · runtime test (L5) pending · tested on dsh 0.1.1-rc.2 · last checked Install verification details →

Data as of (UTC)

What it doesAI

Dsh host auto-update plugin: checks core updates, one-click silent update & restart, plus plugin compatibility diagnostics.

  • Detects @deepseek-ai/dsh host updates across stable/beta/dev channels
  • One-click silent npm update and restart, with major-version confirmation
  • Profile plugin compatibility diagnostic with errors/warnings and fix hints
automationAI

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 dsh-host-update

Install method: npm · sandbox install passed (L4) · runtime test (L5) pending · verified on dsh 0.1.1-rc.2

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.

GitHub stars
0★

current (registry 2026-08-20) · 0 samples; a smoothed curve through every sample — not a daily series

Only 0 points (< 3): no chart yet

no data yet

Weekly star gain
—★

Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend

Only 0 points (< 3): no chart yet

no data yet

Cumulative downloads
—

Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)

Only 0 points (< 3): no chart yet

no data yet

Weekly downloads
920

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

08-22 → 08-26 · 3 points

npm snapshots 82 · 3 observed days · mirror included from 2026-10-18weekly board —total board —downloads ≠ unique usersstar weekly —

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

Declared DSH compatibilityfrom package.json · peerDependencies
only dsh 0.1.x (0.1.0-rc.8 and up, below 0.2.0)

Based on 1 requirement(s) across 2 @deepseek-ai/dsh-* packages.

raw ranges^0.1.0-rc.8 ×2

✗ 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-host-update@0.1.11 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).

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.1.1-rc.2
0.1.11·
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
0.1.11npm2026-08-24

dsh-host-update

No runtime install test for this version (static scan only) — compatibility unknown, never assumed.

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:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-host-update.svg)](https://www.dsh.so/artifact/dsh-host-update/?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.

dsh-host-updateAutomated review · daily

Static low; dynamic medium (authoritative when present) → overall medium.

static low→dynamic medium→overall medium
dynamic findings0 critical·0 high·1 medium·2 low
mediumoverall · medium
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv0.1.11dsh manifest
scanned version0.1.11npm2026-08-26
current version0.1.11same version
vet verdictclean · npm

Vet is an AST static scan (npm artifact or git source).

show static findings (5)
  • criticalchildProcess · code-execlib/index.js:5

    import { exec as execCb, execSync } from "node:child_process";

  • criticalshellExec · shelllib/index.js:62

    const { stdout } = await exec(`npm view ${pkg} dist-tags --json`, { timeout: 10_000 });

  • criticalshellExec · shelllib/index.js:122

    const { stdout } = execSync ? execSync(`npm ${arg} -g`, { encoding: "utf8", timeout: 5000 }) : { stdout: "" };

  • criticalshellExec · shelllib/index.js:340

    const { stdout, stderr } = await exec(`npm i -g @deepseek-ai/dsh@${latest}`, { timeout: 120_000 });

  • warningfsWrite · fileslib/index.js:46

    fs.writeFileSync(path, JSON.stringify(next, null, 2));

2model reads redacted source context · never executes plugin code
highest grademedium
merged intooverall medium
audited at2026-10-16
audited artifactnpm 0.1.11
findings0 critical·0 high1 medium / 2 low hidden
show 3 audit findings
  • mediumnpm dist-tag value from the registry is interpolated into a shell command in /api/host-update/applylib/index.js:345

    `latest` is remote data (npm registry JSON) placed into a shell command string with no shell-metacharacter validation. The semver regex used for the version comparison explicitly allows an arbitrary tail after '+', so a value such as `9.9.9+$(evil)` still passes isUpgrade()/isMajorBump() and would be handed to /bin/sh as a command. Exploitation requires control over the `npm view` response (rogue/compromised npm mirror, .npmrc registry override, or TLS interception) - an attacker who controls that channel could also serve a malicious tarball, so the incremental risk is moderate rather than cri

  • lowsameOrigin() trusts a missing Origin and a client-supplied Host header on state-changing routeslib/index.js:214

    The only guard on POST /api/host-update/settings and POST /api/host-update/apply is this Origin==Host comparison. Requests without an Origin header (any non-browser local process) are allowed, and the comparison can be satisfied by DNS rebinding because Host is attacker-controlled in that scenario (origin host === host header). A rebound page or a local process can therefore drive a host update/major-bump install (forceMajor:true) without user confirmation, and read the status/diag JSON (installed host version + plugin inventory).

  • lowwriteHostUpdateSettings() calls require() inside an ES module, so POST /api/host-update/settings always throwslib/index.js:40

    lib/index.js is ESM (type: module) and does not define `require`, so this line raises ReferenceError every time the POST settings handler runs: the endpoint can never persist enabled/channel, and the rejection is raised inside an async HTTP handler. Depending on whether the host web server catches handler rejections, this is at best a permanently broken setting (the enable/disable toggle advertised to the user does nothing) and at worst an unhandled rejection that can terminate the host process (DoS).

Legit host-updater: 5 local HTTP routes and a shell `npm i -g` call that interpolates an unvalidated npm dist-tag value; no backdoor, secrets or exfiltration found.

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-20 · activity: Inactive

• Repo created: 2026-08-20

• Stars: ★ 0 · Forks: 0

• Health: Inactive — no commit in 90+ days

Source

GitHub: github.com/Trewyn/dsh-host-update

Frequently asked questions

What is dsh-host-update?

dsh-host-update 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-host-update?

Run dsh plugin --profile web add dsh-host-update in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed 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-10-16 (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.

Was this page helpful?