Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.1 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Condition-driven monitoring that watches files, commands, HTTP, processes, and webhooks to wake the agent, with a global dashboard.
- Durable file and process watches
- HTTP and webhook triggers
- Global dashboard and dock integration
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:fuhefei/dsh-sentinel#v0.14.0Install method: GitHub · runtime verified (L5) · verified on dsh 0.2.2-rc.1
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.
current (registry 2026-11-13) · 10 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-11 · 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-28 → 11-11 · 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 3 @deepseek-ai/dsh-* packages. raw ranges
>=0.2.0-rc.2 <0.3.0 ×3
✓ Running dsh 0.2.2-rc.2 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).
| plugin ＼ dsh | dsh 0.2.2-rc.1 | dsh 0.2.2-alpha.2 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v0.14.2 | · | · | · | · | · |
| v0.14.0 | ✓ | ✓ | · | · | · |
| v0.13.2 | · | · | ✓ | ✓ | · |
| v0.13.1 | · | · | · | · | ✓ |
| v0.12.1 | · | · | · | · | · |
v0.14.2github2026-11-13
https://github.com/fuhefei/dsh-sentinel
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
v0.14.0github✓ 2 runtime-verified2026-11-04
https://github.com/fuhefei/dsh-sentinel
✓dsh 0.2.2-rc.12026-11-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/fuhefei/dsh-sentinel#v0.14.0
ID: dsh-sentinel@v0.14.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.2-alpha.22026-11-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-alpha.2
- • Plugin artifact: github · https://github.com/fuhefei/dsh-sentinel#v0.14.0
ID: dsh-sentinel@v0.14.0@dsh0.2.2-alpha.2 · profile: l4-sandbox
Issued: 2026-11-04 · expires: 2026-11-11
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.13.2github✓ 2 runtime-verified2026-10-30
https://github.com/fuhefei/dsh-sentinel
✓dsh 0.2.1-rc.52026-10-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/fuhefei/dsh-sentinel#v0.13.2
ID: dsh-sentinel@v0.13.2@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
View checks & evidence
active in loader tree (150 entries)
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-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/fuhefei/dsh-sentinel#v0.13.2
ID: dsh-sentinel@v0.13.2@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.13.1github✓ 4 runtime-verified2026-10-18
https://github.com/fuhefei/dsh-sentinel
✓dsh 0.2.1-rc.22026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/fuhefei/dsh-sentinel#v0.13.1
ID: dsh-sentinel@v0.13.1@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/fuhefei/dsh-sentinel#v0.13.1
ID: dsh-sentinel@v0.13.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
active in loader tree (150 entries)
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-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/fuhefei/dsh-sentinel#v0.13.1
ID: dsh-sentinel@v0.13.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
active in loader tree (150 entries)
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 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/fuhefei/dsh-sentinel#v0.13.1
ID: dsh-sentinel@v0.13.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.12.1github1 failed2026-10-04
https://github.com/fuhefei/dsh-sentinel
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/fuhefei/dsh-sentinel#v0.12.1
ID: dsh-sentinel@v0.12.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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-sentinel/?ref=badge)``[](https://www.dsh.so/artifact/dsh-sentinel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-sentinel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-sentinel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-sentinel/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-sentinel/?ref=badge-install)`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.14.2dsh manifestv0.14.2git2026-11-13v0.14.2same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalshellExec · shell
src/sensors.ts:73exec(target, { timeout: PROBE_TIMEOUT_MS, maxBuffer: 1024 * 1024 }, (error, stdout, stderr) => { - warningshellExec · shell
src/sensors.ts:120execFile('pgrep', ['-af', target], { timeout: PROBE_TIMEOUT_MS, maxBuffer: 1024 * 1024 }, (_error, stdout) => {
The artifact has changed (audited git 8b57beb904600a74cefab6ea1a965d46c06a4d10 → current git 3edd22b97e3009101ea8e842702c88d2c3265220): the conclusion is still counted conservatively and has been queued for re-audit; it is replaced once that audit lands.
show 5 audit findings
- mediumcommand sensor executes arbitrary agent-supplied shell on a recurring server-side timer
src/sensors.ts:72probeCommand passes the watch target unfiltered to child_process.exec, so any 'command' watch runs an arbitrary shell line on every probe interval, persisting across session sleep. The source comment self-certifies this as a 'deliberate power tool', but a prompt-injected agent (or a malicious note/content steering registration) can register a repeating command executor that keeps firing without further user action, expanding the agent's one-shot shell access into persistent scheduled execution.
- mediumhttp sensor performs server-side fetch of arbitrary agent-supplied URL (SSRF)
src/sensors.ts:89probeHttp fetches any URL the agent puts in a watch target, from the dsh host's network position, and stores the status + up to 8KB body in the sidecar/state. This lets an agent (including a prompt-injected one) reach internal-only endpoints such as cloud metadata (169.254.169.254), localhost admin services, or intranet hosts, with the response surfaced in the dashboard.
- mediumsynchronous user-supplied regex over probe snapshots enables event-loop ReDoS
src/sensors.ts:181normalizeSpec only checks that the pattern compiles; shouldFire then runs it synchronously with .test()/.exec() over snapshots up to ~8KB on every probe. A catastrophic-backtracking pattern (agent-supplied, possibly via prompt injection) blocks the Node.js event loop, stalling the entire dsh host process rather than just this plugin.
- lowport sensor allows arbitrary internal TCP reachability probing
src/sensors.ts:139probePort connects to any host:port the agent supplies and reports open/closed/timeout, giving the agent a scheduled internal port-scan primitive; results persist in the watch state.
- lowfile sensor reads tail of arbitrary agent-chosen path and persists it
src/sensors.ts:51probeFile reads up to 8KB from any path the agent specifies and stores it in the sidecar log and the state route that feeds the dashboard. Because this content is persisted and republished (route auth not visible in the corpus), a watch on a secret-bearing file (e.g. .env, key files) copies it into plugin storage beyond a single read.
Probes are read-only by design, but the command sensor runs arbitrary agent-supplied shell on a timer, HTTP/port sensors enable SSRF, and synchronous user regex allows event-loop ReDoS.
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-11-11 · activity: Active
• Repo created: 2026-08-13
• Stars: ★ 23 · Forks: 6
• Health: Active — committed within last 30 days
Source
GitHub: github.com/fuhefei/dsh-sentinel
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-sentinel?
dsh-sentinel 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-sentinel?
Run dsh plugin --profile web add github:fuhefei/dsh-sentinel#v0.14.2 in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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-13 (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.