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 →
Data as of (UTC)
What it doesAI
Windows tray app that starts/stops dsh web in WSL, shows live status, and adds a desktop shortcut to open it.
- Windows tray icon to start/stop dsh web in WSL
- Live status display for the running service
- Switchable auto start/stop plus desktop shortcut
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-web-trayInstall method: npm · runtime test inconclusive (L5 unknown)
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.
5 samples (roughly every 7 days), 1 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
10-04 → 11-13 · 5 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-09 → 11-13 · 3 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
10-04 → 11-16 · 40 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
10-04 → 11-17 · 41 points
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.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.2-alpha.2 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 |
|---|---|---|---|---|---|
| 1.0.2 | ○ | ○ | ○ | ○ | ○ |
| 0.1.0 | · | · | · | · | · |
1.0.2npm○ 8 ecosystem plugin1 failed2026-11-16
dsh-web-tray
○dsh 0.2.2-rc.3current2026-11-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-web-tray@1.0.2
ID: dsh-web-tray@1.0.2@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-16 · expires: 2026-11-23
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.2-rc.12026-11-13Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-web-tray@1.0.2
ID: dsh-web-tray@1.0.2@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-13 · expires: 2026-11-20
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.2-alpha.22026-11-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-alpha.2
- • Plugin artifact: npm · dsh-web-tray@1.0.2
ID: dsh-web-tray@1.0.2@dsh0.2.2-alpha.2 · profile: l3-fullscan
Issued: 2026-11-04 · expires: 2026-11-11
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-rc.52026-11-02Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-web-tray@1.0.2
ID: dsh-web-tray@1.0.2@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-02 · expires: 2026-11-09
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-rc.32026-10-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-web-tray@1.0.2
ID: dsh-web-tray@1.0.2@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-30 · expires: 2026-11-06
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-rc.22026-10-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-web-tray@1.0.2
ID: dsh-web-tray@1.0.2@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-25 · expires: 2026-11-01
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: npm · dsh-web-tray@1.0.2
ID: dsh-web-tray@1.0.2@dsh0.2.1-alpha.4 · profile: l4-sandbox
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.
✗dsh 0.2.1-alpha.22026-10-14Ecosystem plugin · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-web-tray@1.0.2
ID: dsh-web-tray@1.0.2@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-14 · expires: 2026-10-21
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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-web-tray@1.0.2
ID: dsh-web-tray@1.0.2@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
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.
0.1.0npm✓ 1 runtime-verified2026-10-05
dsh-web-tray
✓prehistory2026-10-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-web-tray@0.1.0
ID: dsh-web-tray@0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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-web-tray/?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 low; dynamic medium (authoritative when present) → overall medium.
v1.0.21.0.2npm2026-11-181.0.2same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (9)
- warningchildProcess · code-exec
bin/dsh-web-tray.mjs:221const child = spawn(powershellPath(), ['-NoProfile', '-NonInteractive', '-ExecutionPolicy', 'Bypass', '-WindowStyle', 'Hidden', ...args], { - warningchildProcess · code-exec
bin/dsh-web-tray.mjs:615const child = spawn(command.file, command.args, { detached: true, stdio: 'ignore', windowsHide: true }) - warningchildProcess · code-exec
bin/dsh-web-tray.mjs:619const child = spawn('bash', [join(layout.targetDir, script)], { detached: true, stdio: 'ignore' }) - warningnetIp · network
bin/dsh-web-tray.mjs:340WEB_URL: `http://127.0.0.1:${port}`, - warningnetIp · network
bin/dsh-web-tray.mjs:531const url = env.WEB_URL ?? `http://127.0.0.1:${DEFAULT_WEB_PORT}` - warningnetIp · network
bin/dsh-web-tray.mjs:565const url = env.WEB_URL ?? `http://127.0.0.1:${DEFAULT_WEB_PORT}` - warningnetIp · network
windows/start.sh:22[ -n "$URL" ] || URL='http://127.0.0.1:3080' - warningcurlDownload · network
windows/start.sh:35code="$(curl -s -o /dev/null -w '%{http_code}' --max-time 2 "$URL" 2>/dev/null)" - warningcurlDownload · network
windows/start.sh:38wget -S -q -O /dev/null -T 2 "$URL" 2>&1 | grep -q 'HTTP/'
show 4 audit findings
- mediumWindows payload dsh-web-tray.ps1 is launched with -ExecutionPolicy Bypass but was not part of the audited source
windows/dsh-web-tray.js:17install copies windows/dsh-web-tray.ps1 verbatim into the user profile directory (WINDOWS_FILES in bin/dsh-web-tray.mjs) and Windows executes it from there with the execution policy disabled, both via the .lnk launcher and via powershell -File during install/uninstall. The .ps1 itself was not included in the harvested source, so the actual code that runs on Windows with the user's token is unaudited, and no hash/integrity check is done on the copy that is later re-executed from a user-writable directory. Anyone or anything able to write that directory (malicious DSH plugin, sync client, anothe
- lowPowerShell executable is resolved from any /mnt/<drive> Windows path, allowing image planting from an extra mounted drive
bin/dsh-web-tray.mjs:179mountedDrives() adds every drive letter seen in PATH and in /proc/mounts, and powershellPath() picks the first candidate that existsSync() finds. On a host where the expected C: path is absent or comes later, a planted Windows\System32\WindowsPowerShell\v1.0\powershell.exe on another mounted volume (e.g. a USB/network drive under /mnt/d) would be executed for shortcut creation and process queries.
- lowstop.sh kills any process whose command line merely contains 'dsh web'
windows/stop.sh:23The candidate set comes from pgrep -f '[d]sh web' and is confirmed only by the loose case pattern *"dsh web"*) in is_dsh_web (line 17), so any process whose /proc/<pid>/cmdline happens to contain the substring 'dsh web' (e.g. an editor, grep, log viewer or a DSH instance started by a different install) is killed with SIGTERM, even though the docs say only instances started from this install are targeted.
- lowisRemovableShortcut prefix check is not normalised, so a crafted stamp path with '..' can delete an arbitrary .lnk
bin/dsh-web-tray.mjs:469shortcutPathFromStamp() feeds stamp.path through windowsDirToWsl() and only endswith('.lnk') plus a startsWith prefix check follows. A stamp such as C:\Users\me\Desktop\..\..\..\other\x.lnk converts to a path that still passes both checks, and install/uninstall would rmSync() that .lnk anywhere on the drive. Writing the stamp requires access to the install directory (same user), so this is a hardening gap rather than an escalation.
No critical/high issues in the WSL CLI; its Windows PowerShell payload is unaudited and runs with ExecutionPolicy Bypass, plus three low-severity hardening gaps.
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-05 · activity: Stable
• Repo created: 2026-10-03
• Stars: ★ 0 · 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 @p455enger/dsh-web-tray?
@p455enger/dsh-web-tray is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 @p455enger/dsh-web-tray?
Run dsh plugin --profile web add dsh-web-tray in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. 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, 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-18 (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.
