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
Windows system tray launcher for DeepSeek Harness web UI with quick access to logs and one-click exit.
- Runs dsh web without a window
- System tray menu for UI, logs, exit
- One-click installation
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 dsh-tray-launcherInstall method: npm · runtime verified (L5) · verified on dsh 0.2.2-rc.3
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.
7 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-16 · 7 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
10-06 → 11-16 · 4 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-11 → 11-17 · 60 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-11 → 11-17 · 60 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 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 1.5.2 | ✓ | ✓ | ✓ | ✓ | ✓ |
| 1.4.2 | · | · | · | · | · |
| 1.4.1 | · | · | · | · | · |
1.5.2npm✓ 9 runtime-verified2026-11-17
dsh-tray-launcher
✓dsh 0.2.2-rc.32026-11-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-tray-launcher@1.5.2
ID: dsh-tray-launcher-2@1.5.2@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-17 · expires: 2026-11-24
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-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-tray-launcher@1.5.2
ID: dsh-tray-launcher-2@1.5.2@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-12 · expires: 2026-11-19
View checks & evidence
active in loader tree (200 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-10-31L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-tray-launcher@1.5.2
ID: dsh-tray-launcher-2@1.5.2@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-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.2.1-rc.32026-10-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-tray-launcher@1.5.2
ID: dsh-tray-launcher-2@1.5.2@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
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-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-tray-launcher@1.5.2
ID: dsh-tray-launcher-2@1.5.2@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: npm · dsh-tray-launcher@1.5.2
ID: dsh-tray-launcher-2@1.5.2@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: npm · dsh-tray-launcher@1.5.2
ID: dsh-tray-launcher-2@1.5.2@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: npm · dsh-tray-launcher@1.5.2
ID: dsh-tray-launcher-2@1.5.2@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.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-tray-launcher@1.5.2
ID: dsh-tray-launcher-2@1.5.2@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
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.
1.4.2npm✓ 5 runtime-verified2026-09-29
dsh-tray-launcher
✓dsh 0.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-tray-launcher@1.4.2
ID: dsh-tray-launcher-2@1.4.2@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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 · dsh-tray-launcher@1.4.2
ID: dsh-tray-launcher-2@1.4.2@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-24L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-tray-launcher@1.4.2
ID: dsh-tray-launcher-2@1.4.2@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
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-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: npm · dsh-tray-launcher@1.4.2
ID: dsh-tray-launcher-2@1.4.2@dsh0.1.7-alpha.2 · 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 · dsh-tray-launcher@1.4.2
ID: dsh-tray-launcher-2@1.4.2@dsh0.1.6-alpha.2 · profile: l3-fullscan
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.
1.4.1npm✓ 2 runtime-verified2026-09-17
dsh-tray-launcher
✓dsh 0.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · dsh-tray-launcher@1.4.1
ID: dsh-tray-launcher-2@1.4.1@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.
✓dsh 0.1.5-rc.22026-09-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-tray-launcher@1.4.1
ID: dsh-tray-launcher-2@1.4.1@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-12 · expires: 2026-09-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.
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-tray-launcher-2/?ref=badge)``[](https://www.dsh.so/artifact/dsh-tray-launcher-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-tray-launcher-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-tray-launcher-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-tray-launcher-2/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-tray-launcher-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 high; dynamic medium (authoritative when present) → overall medium.
v1.5.2dsh manifest1.5.2npm2026-11-191.5.2same versionsuspicious · npmVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningchildProcess · code-exec
bin/dsh-tray-install.js:11const child = spawn("powershell.exe", args, { stdio: "inherit" }); - warningchildProcess · code-exec
bin/dsh-tray.js:16const child = spawn("powershell.exe", psArgs, { stdio: "inherit" }); - warningchildProcess · code-exec
bin/dsh-tray.js:21const child = spawn("powershell.exe", ["-WindowStyle", "Hidden", ...psArgs], { - warningnetIp · network
bin/dsh-tray.js:39console.log("dsh-tray: 已有托盘实例在运行,稍候浏览器会自动打开界面(http://127.0.0.1:3080)。"); - warningchildProcess · code-exec
src/plugin.js:35const child = spawn(
show 3 audit findings
- mediumExecutes bundled PowerShell payloads with ExecutionPolicy Bypass; the .ps1/.vbs bodies are shipped but weren't available for review
bin/dsh-tray-install.js:10Every entry point (src/plugin.js, bin/dsh-tray.js, bin/dsh-tray-install.js) runs local PowerShell/VBScript with the execution policy disabled. package.json ships tray.ps1, install.ps1, uninstall.ps1 and launch-hidden.vbs, but none of them were included in the harvested source, so the code that actually runs with the user's full privileges is unauditable here. Any malicious or merely over-broad behaviour in those scripts (file writes, network calls, autorun registry entries, self-update) would be invisible to this review and would execute automatically.
- lowAuto-registered plugin silently starts a hidden PowerShell background process on every harness start, with output discarded
src/plugin.js:48cordis.patch.yml auto-inserts the plugin, so merely installing it causes a windowless PowerShell process to be spawned on each `dsh web` start (and unref'd, so the harness cannot observe its lifecycle). stdio is discarded, so the user gets no visible trace of what the tray process does or whether it fails; the kill on dispose only signals the PowerShell wrapper, not necessarily a detached tray process. This is a persistence/visibility gap rather than a demonstrated abuse.
- lowCaret-range dependency on a third-party plugin package that this launcher installs/updates on the user's behalf
package.json:19The plugin depends on dsh-plugin-usage-meter with an open caret range, and its own description states it provides one-click install and update of that usage/cost meter plugin. Any future 1.x release of that third-party package (or a compromised publish) would be pulled in and installed without a pinned version, adding an unverified supply-chain hop inside a process that already runs with the user's full desktop privileges.
Windows tray launcher spawns bundled PowerShell with ExecutionPolicy Bypass; the actual .ps1/.vbs payloads are shipped and executed but were not part of the harvest, so they remain unreviewed.
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-29 · activity: Stable
• Repo created: 2026-08-19
• Stars: ★ 6 · Forks: 1
• 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-tray-launcher?
dsh-tray-launcher 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-tray-launcher?
Run dsh plugin --profile web add dsh-tray-launcher 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-19 (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.
