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
DSH task reminder plugin: alerts on task finish or when user decision (approval/question) is needed, via web toast and desktop notifications.
- Floating panel above all apps, Spaces, fullscreen
- Web toast in DSH page plus system banners
- Phone sync of task/alerts via dsh remote bridge
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 @hsinsekai-nanami/dsh-notifierInstall 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.
10 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-13 · 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-24 → 11-13 · 9 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-12 → 11-15 · 58 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-12 → 11-16 · 59 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.5.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
| v0.3.0 | · | · | · | · | · |
0.5.0npm✓ 12 runtime-verified2026-11-16
@hsinsekai-nanami/dsh-notifier
✓dsh 0.2.2-rc.3current2026-11-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@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-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-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.2.1-alpha.22026-10-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-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.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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 · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@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.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@dsh0.1.6-alpha.2 · profile: l4-sandbox
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 · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @hsinsekai-nanami/dsh-notifier@0.5.0
ID: dsh-notifier-2@0.5.0@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-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.
v0.3.0github4 failed2026-09-11
https://github.com/nanami-0713/dsh-notifier
✗dsh 0.1.5-rc.22026-09-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/nanami-0713/dsh-notifier#v0.3.0
ID: dsh-notifier-2@v0.3.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/nanami-0713/dsh-notifier#v0.3.0
ID: dsh-notifier-2@v0.3.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/nanami-0713/dsh-notifier#v0.3.0
ID: dsh-notifier-2@v0.3.0@dsh0.1.3-alpha.1 · profile: l3-fullscan
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/nanami-0713/dsh-notifier#v0.3.0
ID: dsh-notifier-2@v0.3.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
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-notifier-2/?ref=badge)``[](https://www.dsh.so/artifact/dsh-notifier-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-notifier-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-notifier-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-notifier-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-notifier-2/?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.5.0dsh manifest0.5.0npm2026-11-170.5.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (11)
- warningnetIp · network
lib/client.js:29webUrl: "http://127.0.0.1:3080", - warningnetIp · network
lib/client.js:720children: "bridge 地址(如 http://127.0.0.1:8787)" - warningnetIp · network
lib/client.js:724placeholder: "http://127.0.0.1:8787", - warningchildProcess · code-exec
lib/index.js:326const result = spawnSync('swiftc', ['-O', '-swift-version', '5', src, '-o', bin], { - warningchildProcess · code-exec
lib/index.js:375const child = spawn(bin, args, { detached: true, stdio: 'ignore' }); - warningchildProcess · code-exec
lib/index.js:391const hasZenity = spawnSync('which', ['zenity'], { encoding: 'utf8' }).status === 0; - warningshellExec · shell
lib/index.js:285execFile('/usr/bin/osascript', ['-e', script], { timeout: 5000 }, () => { - warningshellExec · shell
lib/index.js:290execFile('notify-send', [title, message], { timeout: 5000 }, () => { - warningshellExec · shell
lib/index.js:301execFile('powershell.exe', ['-NoProfile', '-NonInteractive', '-Command', ps], { timeout: 12000 }, () => { - warningnetIp · network
lib/index.js:33webUrl: process.env.DSH_WEB_URL || 'http://127.0.0.1:3080', - warningnetIp · network
lib/shared.js:27webUrl: 'http://127.0.0.1:3080',
show 3 audit findings
- highWindows toast path builds PowerShell from JSON.stringify, so a quote in the message breaks out and runs commands
lib/index.js:299JSON.stringify escapes double quotes as \", but PowerShell's escape character is the backtick, not the backslash, so a '"' inside message terminates the string literal and the rest is parsed as PowerShell code. message embeds agent-influenced text (errorText(error), toolName, req.reason/event.data.reason), e.g. reason = x"; Start-Process calc; #, giving arbitrary command execution on every win32 host that reaches an approval/error notification.
- mediummacOS fallback dialog embeds config webUrl into do shell script without shell quoting
lib/index.js:383Only double quotes are escaped, so shell metacharacters in webUrl survive into the /bin/sh command executed by osascript. webUrl comes from loader config/config.json and is accepted unvalidated (stringValue, max 512, no URL parsing) by PUT /api/dsh-notifier/config; a value such as http://x; touch /tmp/pwned # executes on macOS whenever the Swift notifier is unavailable (swiftc missing/compile failure) and a sticky approval/question notification fires.
- lowBridge token is stored in plaintext config.json and returned verbatim by the config GET route
lib/index.js:216The plugin route performs no auth or origin check of its own, and the response/response file contain bridgeToken (which may originate from the DSH_BRIDGE_TOKEN environment variable, resolved at line 53 and then persisted). Any local process able to reach the DSH web server can read the token, and it also sits unencrypted on disk.
Verified command-injection sinks: PowerShell string built with JSON.stringify on win32, and unquoted webUrl in a macOS AppleScript do-shell-script fallback; other child_process calls are properly quoted.
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-28 · activity: Stable
• Repo created: 2026-08-15
• Stars: ★ 1 · 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-notifier?
dsh-notifier 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-notifier?
Run dsh plugin --profile web add @hsinsekai-nanami/dsh-notifier 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.
