⚠️ This repository has been renamed: TianzeLuo/dsh-away-notify — click to visit the new location. Everything below is preserved as originally indexed.
Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Sends native desktop toasts for dsh turn completion, errors, approvals, agent questions and goal completion only when you are away; click to return.
- Five trigger types, each independently toggleable
- Sticky Windows reminder toasts; click returns to that session
- Two-level presence suppression with 45s TTL; zero runtime deps
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.
7 samples (roughly every 1 days), 6 of them reconstructed (hollow dots); sampled points, not a daily series
09-17 → 10-12 · 7 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
09-24 → 10-12 · 6 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:s11phere/dsh-away-notifyInstall method: GitHub · runtime verified (L5) · verified on dsh 0.2.1-rc.2
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.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| ead1d0 | ✓ | ✓ | ✓ | ✓ | ✓ |
ead1d0github✓ 9 runtime-verified2026-10-19
https://github.com/s11phere/dsh-away-notify
✓dsh 0.2.1-rc.22026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/s11phere/dsh-away-notify (version unstated)
ID: dsh-away-notify-2@ead1d0@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-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/s11phere/dsh-away-notify (version unstated)
ID: dsh-away-notify-2@ead1d0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-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.2.1-alpha.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/s11phere/dsh-away-notify (version unstated)
ID: dsh-away-notify-2@ead1d0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-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.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/s11phere/dsh-away-notify (version unstated)
ID: dsh-away-notify-2@ead1d0@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.2.0-rc.12026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/s11phere/dsh-away-notify (version unstated)
ID: dsh-away-notify-2@ead1d0@dsh0.2.0-rc.1 · profile: l4-sandbox
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.
✓dsh 0.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/s11phere/dsh-away-notify (version unstated)
ID: dsh-away-notify-2@ead1d0@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-24not tested
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/s11phere/dsh-away-notify (version unstated)
ID: dsh-away-notify-2@ead1d0@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
This level was not executed in this scan.
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: github · https://github.com/s11phere/dsh-away-notify (version unstated)
ID: dsh-away-notify-2@ead1d0@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: github · https://github.com/s11phere/dsh-away-notify (version unstated)
ID: dsh-away-notify-2@ead1d0@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-10-03L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/s11phere/dsh-away-notify (version unstated)
ID: dsh-away-notify-2@ead1d0@dshunknown · profile: l4-sandbox
Issued: 2026-10-03 · expires: 2026-10-10
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.
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-away-notify-2/?ref=badge)``[](https://www.dsh.so/artifact/dsh-away-notify-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-away-notify-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-away-notify-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-away-notify-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 low (authoritative when present) → overall low.
v0.1.0dsh manifest0.1.0git2026-10-180.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningchildProcessImport · code-exec
lib/host.js:21import { spawn } from 'node:child_process'; - warningnetIp · network
lib/host.js:332if (Number.isInteger(port) && port > 0) return `http://127.0.0.1:${port}`; - warningnetIp · network
lib/host.js:336return 'http://127.0.0.1:3080'; - warningchildProcessImport · code-exec
lib/notifier.js:18import { spawn } from 'node:child_process'; - warningbase64Decode · obfuscation
lib/notifier.js:41return [System.Text.Encoding]::UTF8.GetString([Convert]::FromBase64String($b)) - warningbase64Decode · obfuscation
lib/notifier.js:92return [System.Text.Encoding]::UTF8.GetString([Convert]::FromBase64String($b)) - warningchildProcessImport · code-exec
lib/protocol.js:14import { spawnSync } from 'node:child_process';
show 3 audit findings
- lowProtocol/helper launchers (scripts/*.ps1, *.vbs) executed at runtime are absent from the audited source
lib/host.js:30host.js spawns these scripts via wscript/PowerShell at load time and registers a dshnotify: handler that feeds them an attacker-influenceable URI, but the nine harvested files contain no scripts/ directory, so their argument parsing and URL-opening behaviour cannot be reviewed and no risk can be ruled in or out.
- lowWeb auth token is embedded in the dshnotify: URI stored in Windows toast history and process argv
lib/host.js:364With includeToken defaulting to true, the tokenised URL is base64-encoded into the toast launch argument, persisted by Windows notification history and handed to wscript on the command line; any same-user process, log collector or EDR telemetry can recover a credential for the local dsh server.
- lowHKCU dshnotify: protocol handler is registered but never unregistered on plugin unload
lib/host.js:27unregisterProtocol() exists in protocol.js but is never imported or called, so the dispose effect only stops the helper; HKCU\Software\Classes\dshnotify keeps pointing at the plugin's wscript command after removal, holding a stale executable path in the user's shell namespace.
Encoded PowerShell/registry/child_process usage is defensively parameterised; only low-severity audit-coverage and secret-hygiene issues remain.
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-01 · activity: Active
• Repo created: 2026-09-16
• Stars: ★ 2 · Forks: 0
• Health: Active — committed within last 30 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-away-notify?
dsh-away-notify 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-away-notify?
Run dsh plugin --profile web add github:s11phere/dsh-away-notify 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-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.