@MikatoMisaka/dsh-desktop-notify

DSH（DeepSeek Harness）桌面端通知插件：任务完成 / 等待回答时弹 Windows 通知，点通知回到对应会话。

Ecosystem appDesktopAutomationNotifications

Verification

L5 · Ecosystem app

Risk

LowRisk

Health

Active

Trust

Silver

Install verification: Ecosystem app: not installed via dsh plugin add, so the L1-L5 plugin install-verification ladder does not apply; the security scan still runs.

L1–L5 verification rules

What it does

DSH（DeepSeek Harness）桌面端通知插件：任务完成 / 等待回答时弹 Windows 通知，点通知回到对应会话。

Installation

GitHub repository

Ecosystem apps are not installable via dsh plugin add: desktop / web shells install or deploy through their own release channel (GitHub Releases or the project site).

The level reads L5 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (the L1-L5 ladder does not rate them); the security scan still runs.

Verification & Compatibility

No verification record yet for this plugin.

• Node.js: not stated
• DSH: not stated
• External credentials: none detected

Author badges

Embed the official badges in your README to showcase security & install-test status:

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.

dsh-desktop-notify-8Automated review · daily

Static low; dynamic no conclusion (static stands) → overall low.

static low→dynamic no conclusion→overall low

vet findings0 critical·0 high

lowoverall · low

1static scan · vet primaryvet AST static analysis (npm artifact or git source)

Version binding

plugin versionv0.5.0dsh manifest

scanned version0.5.0git2026-10-28

current version0.5.0same version

vet verdictclean · git

Vet is an AST static scan (npm artifact or git source).

show static findings (5)

warningchildProcess · code-execlib/index.js:332
child = spawn(
warningchildProcess · code-execlib/index.js:378
const child = spawn(command, args, { windowsHide: true, stdio: 'ignore', detached: false })
warningshellExec · shelllib/index.js:547
execFile(
warningshellExec · shelllib/index.js:822
execFileSync('reg', ['add', PROTOCOL_KEY, '/ve', '/d', 'URL:dsh-notify', '/f'], options)
warningshellExec · shelllib/index.js:823
execFileSync('reg', ['add', PROTOCOL_KEY, '/v', 'URL Protocol', '/d', '', '/f'], options)

2dynamic auditmodel reads redacted source context · never executes plugin code

not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.

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-10-28 · activity: Active

• Repo created: 2026-10-27

• Stars: ★ 1 · Forks: 0

• Health: Active — committed within last 30 days

Source

GitHub: github.com/MikatoMisaka/dsh-desktop-notify

Plugin notes

What is @MikatoMisaka/dsh-desktop-notify?

@MikatoMisaka/dsh-desktop-notify is an ecosystem app maintained by @MikatoMisaka, not a DSH plugin package — it cannot be installed via dsh plugin add; desktop / web shells ship through the project's own release channel. It is cataloged on dsh.so as a Desktop entry, with a public source repository and automated static security scan.

How do I install @MikatoMisaka/dsh-desktop-notify?

This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. Its level reads L5 · Ecosystem app; the security scan still runs.

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 (it can produce false positives and miss context), and the dynamic security audit has a model read the harvested source context with secret files stripped and content redacted inline — plugin code is never executed. The dynamic audit only covers plugins static-flagged at warn or above; when it reaches a conclusion that conclusion is authoritative for the combined verdict — it may raise or lower it — and the static scan verdict (vet primary, dsh backstop) applies only when there is none. Exemptions stay manual: the audit never writes the suppression list. Neither layer is a manual security audit or an endorsement; before using a plugin, review the repository and installed permissions, and combine both with the verification level (L4/L5) and health signals.

"DeepSeek Harness (dsh) is an open-source agent harness developed by DeepSeek AI. It uses an architecture where everything is a plugin, and is powered by Cordis."
— DeepSeek Harness README

Sources: GitHub repository · DeepSeek Harness README · security scan data · Maintained by dsh.so · Last updated 2026-10-28