Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Desktop notifications for DeepSeek Harness (dsh) — run completion, questions, approvals. Zero-dependency Cordis plugin.
- Notifies on run completion
- Alerts for questions and approvals
- Zero-dependency Cordis plugin
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:pitetow/dsh-notify-on-completeInstall method: GitHub · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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.
11 samples (roughly every 7 days), 5 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-14 · 11 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-14 · 10 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
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
Only 0 points (< 3): no chart yet
no data yet
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
Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages. raw ranges
^0.1.0-rc.5 ×1
✗ Running dsh 0.2.2-rc.3 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-notify-on-complete@0.3.0 0.2.2-rc.3 (the exemption lives in the local profile; this site does not assume one)
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| cc7965 | ✗ | ✗ | ✗ | ✗ | ✗ |
| 2a325b | · | · | · | · | · |
cc7965github16 failed2026-11-14
https://github.com/pitetow/dsh-notify-on-complete
✗dsh 0.2.1-rc.52026-10-31L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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.2.1-rc.32026-10-27L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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.2.1-rc.22026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
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-27L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
View checks & evidence
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/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@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-21L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-21 · expires: 2026-09-28
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
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 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-13 · expires: 2026-09-20
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-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-16
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/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.1.3-alpha.1 · profile: l4-sandbox
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-06L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · github:pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.1.2-rc.1 · profile: l5-web-smoke
Issued: 2026-09-06 · expires: 2026-12-05
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-alpha.12026-09-06L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dsh0.1.2-alpha.1 · profile: l3-fullscan
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/pitetow/dsh-notify-on-complete (version unstated)
ID: dsh-notify-on-complete@cc7965@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
2a325bgithub2026-08-28
https://github.com/pitetow/dsh-notify-on-complete
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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-notify-on-complete/?ref=badge)`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 high; dynamic medium (authoritative when present) → overall medium.
v0.3.0dsh manifest0.3.0git2026-11-140.3.0same versionsuspicious · gitVet is an AST static scan (npm artifact or git source).
show static findings (2)
- warningpipeShell · shell
scripts/install.sh:68die "检测到非交互终端（如 curl | bash），无法询问确认。请加 --yes 跳过确认：bash -s -- --force --yes" - warningcurlDownload · network
scripts/install.sh:84curl -fsSL "https://codeload.github.com/${REPO}/tar.gz/refs/heads/${BRANCH}" -o "${TMP}/src.tgz" \
show 2 audit findings
- mediumModel/session-derived text flows into an unreviewed OS-notify spawner
src/index.ts:104The `detail` argument originates from model-controlled `ask_user_question` arguments (`blockedQuestionText(data.arguments)` in src/notifier.ts) and session titles are model-generated. `buildCommands`/`spawnNotify` live in src/notify.ts, which is imported but absent from the reviewed snapshot. If that module assembles a shell string (exec/execSync) instead of an argv array, model output could inject shell commands. It cannot be confirmed or cleared from the available code.
- lowSettings read/write route has no authentication or origin check
src/api.ts:125The prefix route `/notify-on-complete/api` (registered in src/index.ts:69-72) serves GET/POST `config` with no auth or CSRF/origin gate; any client able to reach the web server can read the config (secrets redacted via `describe({ redactSecrets: true })`) and rewrite this plugin's notification settings through `settings.mutate`. Blast radius is limited to this namespace (no code execution or secret disclosure observed).
Visible code is defensive, but the OS-notify spawner fed by model/session text (src/notify.ts) is missing from the snapshot, so shell-injection risk is unverified; settings route lacks auth.
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-03 · activity: Stable
• Repo created: 2026-08-14
• Stars: ★ 5 · 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-notify-on-complete?
dsh-notify-on-complete 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-notify-on-complete?
Run dsh plugin --profile web add github:pitetow/dsh-notify-on-complete in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run yet.
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-14 (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.