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
Makes DeepSeek Harness session status obvious via a glanceable grid, phone notifications (ntfy), and local alarms.
- Glanceable status grid at /obvious grid
- Sends ntfy notifications on turn finish, error, approval
- Plays local alarm for AFK attention
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-obvious-gridInstall method: npm · runtime verified (L5) · verified on dsh 0.2.2-rc.3
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.
9 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-05 · 9 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-05 · 8 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-21 → 11-17 · 78 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
08-21 → 11-18 · 79 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 | 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.2.2 | ✓ | ○ | ✓ | ✓ | ✓ |
0.2.2npm✓ 15 runtime-verified2026-11-16
dsh-obvious-grid
✓dsh 0.2.2-rc.32026-11-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@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-12not tested
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-12 · expires: 2026-11-19
View checks & evidence
inventory probe failed (rpc-error) — inconclusive, not a plugin verdict (reinterpreted 2026-11-17)
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-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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 · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.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.
✓dsh 0.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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 · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@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 · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@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 · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@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.1.7-rc.22026-09-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@dsh0.1.7-rc.2 · profile: l3-fullscan
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.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@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-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-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.1.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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.22026-09-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-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.1.3-alpha.12026-09-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
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.
✓dsh 0.1.2-rc.12026-09-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
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-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-obvious-grid@0.2.2
ID: dsh-obvious-grid@0.2.2@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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.
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-obvious-grid/?ref=badge)``[](https://www.dsh.so/artifact/dsh-obvious-grid/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-obvious-grid/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-obvious-grid/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-obvious-grid/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-obvious-grid/?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.2.2dsh manifest0.2.2npm2026-11-190.2.2same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (2)
- criticalspawnShell · shell
lib/notify.js:113child = spawn(alarmCmd, { shell: true, detached: true, stdio: "ignore" }) - warningfsWrite · files
lib/notify.js:45fs.writeFileSync(tmp, JSON.stringify(next, null, 2) + "\n")
show 4 audit findings
- mediumUnauthenticated /obvious-grid/notify POST can repoint the ntfy topic and enable notifications
lib/index.js:199The POST handler writes topic and per-session toggles into the persistent user config with no auth token, Origin/Sec-Fetch-Site check or CSRF protection (the body is text/plain, so a cross-origin simple request succeeds without preflight). Because maybeNotify uses `const topic = userCfg.topic || config.topic` and the push body contains session title, cwd and last error text, any caller that can reach the route can (a) read /obvious-grid/status for a session id, (b) POST {sessionID, enabled:true} to turn notifications on for it, then (c) POST {topic:'attacker-topic'} so all subsequent pushes —
- lowStatus route discloses session titles, cwd, branch, pid and error text without auth
lib/index.js:191GET /obvious-grid/status returns the full snapshot(): sessionTitle, cwd, git branch, parentID, pid, message/token counts and lastError strings for every live session, with no authentication or origin check at this layer. If the host web server is reachable by anything other than the local user, this is a plain information-disclosure endpoint (and it is the enumeration step that makes the /obvious-grid/notify issue exploitable).
- lowplayAlarm spawns alarmCmd with shell:true, but the value is operator config only
lib/notify.js:113This is the construct a pattern scanner flags as command injection, but it is not remotely reachable: alarmCmd originates exclusively from the plugin config schema (`alarmCmd: z.string().default("")`) / the profile's cordis.patch.yml and is never set by the HTTP routes (the POST handler only accepts topic, sessionID and enabled). Running it through a shell is the documented feature (user-supplied sound command). Residual risk is limited to someone who can already edit the DSH profile configuration, i.e. code execution they already possess.
- lowreadBody buffers an unbounded request body in memory
lib/index.js:69The POST body is accumulated into a string with no size cap or timeout; a caller able to reach /obvious-grid/notify can grow harness memory until the JSON.parse/process pressure degrades the host. Impact is limited to availability and requires route reachability, since parsing errors are swallowed.
No RCE path found: alarmCmd comes only from operator config. The unauthenticated /obvious-grid/notify route can repoint ntfy pushes to an attacker-chosen topic.
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-17 · activity: Inactive
• Repo created: 2026-08-16
• 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-obvious-grid?
dsh-obvious-grid 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-obvious-grid?
Run dsh plugin --profile web add dsh-obvious-grid 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-19 (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.
