Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
What it doesAI
Service-type DSH plugin that pushes out-of-band alerts to the owner via Telegram, with dedup, cooldown and disk logging.
- Service-only channel: no tools, exposes a cordis 'notify' service
- Telegram dual-channel delivery with dedup and cooldown
- Logs alerts to disk; only sends, never judges, retries or re-arms
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:jonah791/dsh-agent-notifyInstall method: GitHub · runtime test inconclusive (L5 unknown)
Verification & Compatibility○ Ecosystem plugin
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 current | dsh 0.2.1-alpha.4 |
|---|---|---|
| 4387cc | ○ | ○ |
| 3aac7b | · | · |
4387ccgithub○ 2 ecosystem plugin2026-10-19
https://github.com/jonah791/dsh-agent-notify
○dsh 0.2.1-rc.2current2026-10-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-notify (version unstated)
ID: dsh-agent-notify-2@4387cc@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
not present in web-profile loader inventory
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-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/jonah791/dsh-agent-notify (version unstated)
ID: dsh-agent-notify-2@4387cc@dsh0.2.1-alpha.4 · profile: l3-fullscan
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
3aac7blocal2026-10-15
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-agent-notify-2/)`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 — stricter wins → overall low.
v0.1.00.1.0git2026-10-210.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningnetIp · network
src/index.ts:65proxy: z.string().default('http://127.0.0.1:16888'), - warningchildProcess · code-exec
src/transport.ts:90const child = spawn(process.execPath, ['-e', FETCH_SCRIPT, url, body, outPath], { - warningchildProcess · code-exec
src/transport.ts:114const child = spawn('curl.exe', [ - warningnetIp · network
src/transport.ts:172const proxy = opts.proxy || 'http://127.0.0.1:16888' - warningfsWrite · files
src/transport.ts:61.then((t) => { fs.writeFileSync(outPath, t, 'utf8') }) - warningfsWrite · files
src/transport.ts:62.catch((e) => { fs.writeFileSync(outPath, 'ERR ' + String(e), 'utf8'); process.exit(2) })
show 2 audit findings
- lowBot token is passed in child-process argv, exposing it to other local users via process listings
src/transport.ts:162The full Telegram API URL (containing the bot token) is an argument of the spawned node process, and the curl fallback puts it on curl.exe's command line as well. On a multi-user host the token is readable from /proc/<pid>/cmdline or Windows process/WMI listings, allowing another local account to take over the bot and read/impersonate messages.
- lowResponse handoff uses a predictable filename in the shared temp directory
src/transport.ts:87The child process writes its response to a file whose name is derived only from pid and millisecond timestamp inside the world-writable temp dir, then the parent reads and deletes it. A local attacker able to pre-create that path (e.g. as a symlink) could redirect the write to another file owned by the host user or control the data the parent parses; guessing pid+ms makes exploitation impractical, hence low.
Telegram alert-only plugin; spawns node/curl without a shell to a hardcoded api.telegram.org URL; no injection or exfiltration beyond the operator's own bot; only low-severity hardening gaps.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-10-15 · activity: Active
• Repo created: 2026-10-15
• Stars: ★ 0 · 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).