dsh-server-monitor avatar

dsh-server-monitor

SSH server monitor and terminal sidebar for DeepSeek Harness

PluginNetworkTerminalDesktopTerminal / ShellStorage
Verification
L4 · Install tested
Failed
Risk
Medium
Health
Active
Trust
Silver

Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →

Data as of (UTC)

What it doesAI

Read-only Linux server monitor for the DSH sidebar showing CPU, memory, disk, process, container, network and port stats over SSH.

  • Manage multiple Linux SSH profiles with key or password auth
  • Shows CPU, memory, swap, disk, process, container and network data
  • Read-only, auto-refreshes every 15s while sidebar is visible
networkAIterminalAIstorageAI

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.

GitHub stars
0★

4 samples (roughly every 7 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series

09-18 → 10-19 · 4 points

Weekly star gain
+0★

Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points

10-01 → 10-19 · 3 points

Cumulative downloads
3.7k

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

09-21 → 10-31 · 39 points

Weekly downloads
217

The snapshot’s last-week rolling window (official npm + npmmirror combined)

09-21 → 10-31 · 39 points

npm snapshots 67 · 39 observed days · mirror included from 2026-10-18weekly board #2606total board #1326star weekly —

Installation

dsh plugin --profile web add @goodandready/dsh-server-monitor
verified 0.1.20

Install method: npm · sandbox install ok, web smoke failed (L5)

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 · peerDependenciesdeclared in 0.1.17
supports any of: dsh 0.1.x or dsh 0.2.x

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

raw ranges^0.1.7-rc.2 || ^0.2.0-rc.1 ×3

✓ Running dsh 0.2.1-rc.5 is within the declared range — install is not blocked by version.

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.2.1-rc.5
current
dsh 0.2.1-rc.3dsh 0.2.1-rc.2dsh 0.2.1-alpha.4dsh 0.2.1-alpha.2
0.1.20✗✗···
0.1.19··✗··
0.1.18···✗·
0.1.17····✗
0.1.16·····
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
0.1.20npm2 failed2026-11-01

@goodandready/dsh-server-monitor

✗dsh 0.2.1-rc.5current2026-11-01L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-rc.5
  • • Plugin artifact: npm · @goodandready/dsh-server-monitor@0.1.20
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Failed
Sandbox install failed
L5 · failed

ID: dsh-server-monitor@0.1.20@dsh0.2.1-rc.5 · profile: l4-sandbox

Issued: 2026-11-01 · expires: 2026-11-08

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-30
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-30
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-11-01
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 2.7s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-11-01
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 2.7s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-11-01
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 2.7s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-11-01
spec @goodandready/dsh-server-monitor · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

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-27L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-rc.3
  • • Plugin artifact: npm · @goodandready/dsh-server-monitor@0.1.20
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Failed
Sandbox install failed
L5 · failed

ID: dsh-server-monitor@0.1.20@dsh0.2.1-rc.3 · profile: l4-sandbox

Issued: 2026-10-27 · expires: 2026-11-03

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-30
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-30
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-27
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 4.7s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-27
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 4.7s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-27
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 4.7s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-27
spec @goodandready/dsh-server-monitor · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

0.1.19npm1 failed2026-10-21

@goodandready/dsh-server-monitor

✗dsh 0.2.1-rc.22026-10-21L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-rc.2
  • • Plugin artifact: npm · @goodandready/dsh-server-monitor@0.1.19
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Failed
Sandbox install failed
L5 · failed

ID: dsh-server-monitor@0.1.19@dsh0.2.1-rc.2 · profile: l3-fullscan

Issued: 2026-10-21 · expires: 2026-10-28

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-30
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-30
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 7.3s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 7.3s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 7.3s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-19
spec @goodandready/dsh-server-monitor · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

0.1.18npm1 failed2026-10-18

@goodandready/dsh-server-monitor

✗dsh 0.2.1-alpha.42026-10-17L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.4
  • • Plugin artifact: npm · @goodandready/dsh-server-monitor@0.1.18
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Failed
Sandbox install failed
L5 · failed

ID: dsh-server-monitor@0.1.18@dsh0.2.1-alpha.4 · profile: l4-sandbox

Issued: 2026-10-17 · expires: 2026-10-24

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-30
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-30
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 21.0s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 21.0s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 21.0s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-17
spec @goodandready/dsh-server-monitor · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
boot failed
HTTP endpoint served✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

0.1.17npm2 failed2026-10-15

@goodandready/dsh-server-monitor

✗dsh 0.2.1-alpha.22026-10-11L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.1-alpha.2
  • • Plugin artifact: npm · @goodandready/dsh-server-monitor@0.1.17
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Failed
Sandbox install failed
L5 · failed

ID: dsh-server-monitor@0.1.17@dsh0.2.1-alpha.2 · profile: l4-sandbox

Issued: 2026-10-11 · expires: 2026-10-18

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-30
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-30
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-11
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 9.7s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-11
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 9.7s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-11
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 9.7s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-11
spec @goodandready/dsh-server-monitor · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
boot failed
HTTP endpoint served✕ Failed

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
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.2.0-rc.2
  • • Plugin artifact: npm · @goodandready/dsh-server-monitor@0.1.17
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Failed
Sandbox install failed
L5 · failed

ID: dsh-server-monitor@0.1.17@dsh0.2.0-rc.2 · profile: l4-sandbox

Issued: 2026-10-09 · expires: 2026-10-16

View checks & evidence
L1 · Found✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L2 · Structured✓ Passed
Defaulted from L3✓ Passed
defaulted to passed — L3 install spec passed (full-registry L3 sweep policy)
L3 · Install spec✓ Passed
Install command parsed✓ Passed
Source: registry verification · Method: install spec parse · Captured 2026-10-30
DSH version declared✓ Passed
Source: registry verification · Method: DSH version declaration · Captured 2026-10-30
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-09
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 8.1s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-09
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 8.1s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-09
spec @goodandready/dsh-server-monitor · channel npm package · outcome ran · exit 0
check took: 8.1s
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-10-09
spec @goodandready/dsh-server-monitor · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

0.1.16npm2026-10-08

@goodandready/dsh-server-monitor

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-server-monitor.svg)](https://www.dsh.so/artifact/dsh-server-monitor/?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-server-monitorAutomated review · daily

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

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

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

show static findings (9)
  • warningfsWrite · fileslib/metric-store.js:69

    fs.writeFileSync(file, body ? `${body}\n` : '');

  • warningfsWrite · fileslib/metric-store.js:98

    fs.appendFileSync(path.join(dir, 'raw.jsonl'), `${JSON.stringify(point)}\n`);

  • warningfsWrite · fileslib/metric-store.js:156

    fs.writeFileSync(file, JSON.stringify(next));

  • warningchildProcess · code-execlib/plugin-updater.js:166

    const child = spawn(cmd, args, {

  • warningnetIp · networklib/pty-bridge.js:78

    const url = new URL(req.url || '/', 'http://127.0.0.1');

  • warningshellExec · shelllib/vault-service.js:21

    execFile(icaclsPath, args, { stdio: 'pipe', windowsHide: true });

  • warningfsWrite · fileslib/vault-service.js:38

    fs.chmodSync(filePath, 0o600);

  • warningfsWrite · fileslib/vault-service.js:57

    fs.writeFileSync(this.envPath, '# DSH Server Monitor secrets\n', { encoding: 'utf8', mode: 0o600 });

  • warningfsWrite · fileslib/vault-service.js:123

    fs.writeFileSync(this.envPath, lines.join('\n'), { encoding: 'utf8', mode: 0o600 });

2model reads redacted source context · never executes plugin code
highest grademedium
merged intooverall medium
audited at2026-10-23
findings0 critical·0 high2 medium / 1 low hidden
show 3 audit findings
  • mediumAgent tool server_monitor_exec runs arbitrary SSH commands with stored credentialslib/agent-tools.js:63

    Any party able to steer the harness agent (e.g. prompt injection in monitored data or chat content) can invoke this tool with an arbitrary command string and get it executed on the user's saved hosts under the vault credentials; there is no allowlist, confirmation step, or read-only restriction. The same applies to server_monitor_kill and server_monitor_service.

  • mediumPOST to update endpoint spawns `dsh plugin add`, executing npm lifecycle scripts of a remotely resolved versionlib/plugin-updater.js:166

    A client that passes isTrustedRequest can trigger an npm install of the plugin package at the version returned by the configured registry; npm install runs the package's lifecycle scripts, i.e. code execution from the network. If the isTrustedRequest gate (not in this bundle) is weak, or the configured registry/published package is compromised, this becomes remote code execution triggered over HTTP.

  • lowWindows ACL enforcement failure on the secrets file is only warned, never fatallib/vault-service.js:23

    On Windows, POSIX mode 0600 is a no-op, so the SSH password/private-key vault relies entirely on icacls; if icacls is missing or fails, the plugin continues silently and the file may keep inherited ACLs readable by other local users.

Legitimate SSH monitoring plugin; real residual risk is deliberate remote-command execution (agent tools, auto-updater) behind an auth helper not included in the bundle.

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-10-21 · activity: Active

• Repo created: 2026-09-17

• Stars: ★ 0 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/GooDAnDReaDY/dsh-server-monitor

Frequently asked questions

What is dsh-server-monitor?

dsh-server-monitor 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-server-monitor?

Run dsh plugin --profile web add @goodandready/dsh-server-monitor 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-11-01 (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?