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
Provides an always-on-top agent lamp board and a session context lens for DeepSeek Harness on macOS.
- Always-on-top agent lamp board for macOS.
- Session context lens for inspecting agent session context.
- Part of the DeepSeek Harness plugin set.
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.
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); the npm pair from every snapshot.
4 samples (roughly every 7 days), 1 of them reconstructed (hollow dots); sampled points, not a daily series
09-22 → 10-27 · 4 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
Only 2 points (< 3): no chart yet
10-20 → 10-27 · 2 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
The snapshot’s last-week rolling window (official npm + npmmirror combined)
Only 0 points (< 3): no chart yet
no data yet
Installation
dsh plugin --profile web add github:Xinyuan-Gao/xy-dshInstall 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
package manifest not collected — the declared range is unknown.
| plugin ＼ dsh | dsh 0.2.1-rc.5 current | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 |
|---|---|---|---|---|---|
| a182e4 | · | · | · | · | · |
| 00b31f | ○ | ○ | ○ | ○ | ○ |
a182e4local2026-09-17
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L5 · Ecosystem plugin.
00b31fgithub○ 10 ecosystem plugin2026-10-31
https://github.com/Xinyuan-Gao/xy-dsh
○dsh 0.2.1-rc.5current2026-10-31Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/Xinyuan-Gao/xy-dsh (version unstated)
ID: xy-dsh@00b31f@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
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-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/Xinyuan-Gao/xy-dsh (version unstated)
ID: xy-dsh@00b31f@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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-19Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/Xinyuan-Gao/xy-dsh (version unstated)
ID: xy-dsh@00b31f@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.22026-10-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/Xinyuan-Gao/xy-dsh (version unstated)
ID: xy-dsh@00b31f@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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.0-rc.22026-10-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/Xinyuan-Gao/xy-dsh (version unstated)
ID: xy-dsh@00b31f@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.
○dsh 0.1.7-rc.22026-09-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/Xinyuan-Gao/xy-dsh (version unstated)
ID: xy-dsh@00b31f@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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.1.7-rc.12026-09-24Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/Xinyuan-Gao/xy-dsh (version unstated)
ID: xy-dsh@00b31f@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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/Xinyuan-Gao/xy-dsh (version unstated)
ID: xy-dsh@00b31f@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
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.1.6-alpha.12026-09-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/Xinyuan-Gao/xy-dsh (version unstated)
ID: xy-dsh@00b31f@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/Xinyuan-Gao/xy-dsh (version unstated)
ID: xy-dsh@00b31f@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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.
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/xy-dsh/?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 low (authoritative when present) → overall low.
—ab82e6360132git2026-11-01ab82e6360132same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningnetIp · network
docs/make-assets.py:214url = f"http://127.0.0.1:{port}/" - warningnetIp · network
docs/make-intro.py:165page.goto(f"http://127.0.0.1:{port}/", wait_until="load") - warningchildProcess · code-exec
xy-dsh-lamp/index.mjs:41spawn('osascript', ['-e', script], { detached: true, stdio: 'ignore' }).unref() - warningchildProcess · code-exec
xy-dsh-lamp/index.mjs:45spawn('notify-send', ['-a', 'DeepSeek Harness', title, body], { detached: true, stdio: 'ignore' }).unref() - warningchildProcess · code-exec
xy-dsh-lamp/index.mjs:50spawn('powershell', ['-NoProfile', '-Command', ps], { detached: true, stdio: 'ignore' }).unref() - warningshellExec · shell
xy-dsh-lamp/index.mjs:108execFileSync('swiftc', [hudSource, '-O', '-o', staged, '-framework', 'Cocoa', '-framework', 'WebKit'], { - warningnetIp · network
xy-dsh-lamp/index.mjs:165const page = `http://127.0.0.1:${port}/`
show 3 audit findings
- lowLoopback status server returns session metadata to any requester without Host/Origin checks
xy-dsh-lamp/index.mjs:132server.listen(0, '127.0.0.1') removes the network exposure, but the handler ignores Host and Origin, so any local process - or a page using DNS rebinding against the ephemeral port - can read the snapshot (session titles that usually contain the user's prompt, project directory names, agent states) and can POST /lang to alter the stored language. Plain cross-origin fetches are blocked only because no CORS headers are sent.
- lowNative HUD is compiled from hud.swift and renders overlay.html, neither of which is in the audited source
xy-dsh-lamp/index.mjs:108The plugin builds and launches an AppKit/WebKit process with the user's privileges on every load (line 169: spawn(bin, [page])). hud.swift and overlay.html are referenced at lines 11 and 10 and read by docs/make-assets.py, but are absent from the harvested source, so the executable UI code and everything the WebView page does cannot be reviewed. The reused binary is only mtime-checked against hud.swift, which is not an integrity check.
- lowSIGTERM is sent to whatever pid the pid file holds, so a stale file can hit an unrelated process
xy-dsh-lamp/index.mjs:68killOldHud() reads ~/.dsh/xy-dsh-lamp-hud.pid and signals that number without verifying it is still the HUD. If a crash leaves the file behind and the pid is later reused by another same-user process (plugin load or unload), that process is terminated.
Local DSH UI plugin; notification and HTTP paths are correctly escaped. Residual low risks: unauthenticated loopback status server, unreviewed native HUD source, pid-file kills.
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-02 · activity: Stable
• Repo created: 2026-09-17
• Stars: ★ 0 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/Xinyuan-Gao/xy-dsh
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 xy-dsh?
xy-dsh 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 xy-dsh?
Run dsh plugin --profile web add github:Xinyuan-Gao/xy-dsh 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-01 (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.