Real-time chain-of-thought anchoring monitor & intervention plugin for DeepSeek Harness: three-band (spec/mixed/react) fingerprint detection, L1 hint / L2 reset / L3 restart interventions, liquid-glass web overlay + rheostat bar, standalone monitor process with JSONL experiment logs.
Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · 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
Real-time chain-of-thought anchoring monitor and intervention plugin for DeepSeek Harness with web overlay.
- Three-band spec/mixed/react fingerprint detection
- L1 hint / L2 reset / L3 restart interventions
- Liquid-glass web overlay with rheostat control
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 @a9i5k4/dsh-anchored-monitorInstall method: npm · runtime verified (L5)
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), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-11 · 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-06 → 11-11 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-11 → 11-15 · 59 points
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
09-11 → 11-16 · 60 points
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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 0.3.1 | ✓ | ✓ | ✓ | ✓ | ✓ |
| v0.3.0 | · | · | · | · | · |
0.3.1npm✓ 16 runtime-verified2026-11-16
@a9i5k4/dsh-anchored-monitor
✓dsh 0.2.2-rc.3current2026-11-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
View checks & evidence
active in loader tree (206 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✓dsh 0.2.2-rc.12026-11-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@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.1-rc.52026-10-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@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: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@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.
✓dsh 0.2.1-rc.22026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.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: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.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.
✓dsh 0.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-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.1.7-rc.22026-09-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-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.
✓dsh 0.1.7-rc.12026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.1.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
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.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.1.5-rc.22026-09-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
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.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @a9i5k4/dsh-anchored-monitor@0.3.1
ID: dsh-anchored-monitor@0.3.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-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.3.0github✓ 2 runtime-verified2026-09-11
https://github.com/Aik358/dsh-anchored-monitor
✓dsh 0.1.3-alpha.22026-09-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/Aik358/dsh-anchored-monitor#v0.3.0
ID: dsh-anchored-monitor@v0.3.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
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.1.3-alpha.12026-09-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/Aik358/dsh-anchored-monitor#v0.3.0
ID: dsh-anchored-monitor@v0.3.0@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (151 entries)
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-anchored-monitor/?ref=badge)``[](https://www.dsh.so/artifact/dsh-anchored-monitor/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-anchored-monitor/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-anchored-monitor/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-anchored-monitor/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-anchored-monitor/?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 high (authoritative when present) → overall high.
v0.3.1dsh manifest0.3.1npm2026-11-170.3.1same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- warningchildProcess · code-exec
lib/index.js:175monitorProc = spawn(process.execPath, [MONITOR_ENTRY, '--profile', config.profile, '--overrides', overridesPath()], { - warningnetIp · network
lib/index.js:33const DEFAULT_MONITOR_URL = 'http://127.0.0.1:9301' - warningnetIp · network
lib/index.js:664next.monitorUrl = 'http://127.0.0.1:' + port - warningnetIp · network
preset/anchored-monitor.mjs:21monitorUrl: 'http://127.0.0.1:9301',
show 4 audit findings
- highLoopback guard ignores Origin: cross-site POST can repoint the monitor and hijack interventions
lib/index.js:66The guard only checks req.socket.remoteAddress and the Host header, both of which are loopback for a request sent by a browser on the same machine; no Origin/Sec-Fetch-Site is checked and readJsonBody ignores Content-Type. Any page the user visits can therefore send a simple no-preflight POST to /api/anchored-monitor/config (or /settings) setting monitorUrl to an attacker host. From there all reasoning/visible text is exfiltrated, and the attacker's answers to /api/sessions are executed as L1/L2/L3 interventions (persona/systemPrompt replacement, tool shrinking, followup user-message injection
- mediummonitorUrl accepts any http(s) origin; all reasoning and assistant text are POSTed there
lib/index.js:611No allowlist keeps the endpoint on loopback, no warning is surfaced, and the same free-form value is also read from ~/.dsh/anchored-monitor.json and ANCHORED_MONITOR_URL. Pointing it at a remote host silently ships the complete chain-of-thought and visible answer text off-box, and makes the remote host the source of truth for interventions.
- mediumMonitor endpoint is trusted unauthenticated; a squatter on 127.0.0.1:9301 receives CoT and dictates system prompts
lib/index.js:167Readiness is decided purely by a 200 from /api/health, so any local process that binds the port first suppresses the real monitor and is then fed all reasoning/text; its returned interventions are executed with signal.payload.reset.systemPrompt pushed verbatim into the persona section and signal.payload.hintText injected as a user message.
- lowSpawned monitor executable dist/monitor/index.js is outside the reviewed source set
lib/index.js:174A detached, long-running process with the user's privileges receives the full chain-of-thought stream and serves the intervention API, but its code is not part of the audited files, so its behaviour cannot be confirmed here.
Loopback guard lacks Origin checks, so a web page can repoint the monitor URL, exfiltrating all chain-of-thought and injecting attacker-supplied system prompts into the agent.
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-09-05 · activity: Stable
• Repo created: 2026-08-17
• Stars: ★ 13 · Forks: 0
• Health: Stable — committed within 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-anchored-monitor?
dsh-anchored-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-anchored-monitor?
Run dsh plugin --profile web add @a9i5k4/dsh-anchored-monitor 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-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.
