This repository has been renamed: acdsh4869/dsh-deepseek-web-relay — click to visit the new location. Everything below is preserved as originally indexed.
Install verification: runtime verified (L5) · tested on dsh 0.2.0-rc.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
DSH plugin that opens chat.deepseek.com in a standalone window via a sidebar menu, persisting login and syncing selected text both ways over CDP.
- Sidebar menu item opens chat.deepseek.com in a dedicated window
- Login state persists across sessions
- Bidirectional selected-text transfer between DSH and the web page via CDP
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:acdsh4869/dsh-DeepSeek-chat#v1.0.0Install method: GitHub · runtime verified (L5) · verified on dsh 0.2.0-rc.2
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.0-rc.2 | dsh 0.2.0-rc.1 | prehistory |
|---|---|---|---|
| v1.0.0 | ✓ | · | ✓ |
v1.0.0github✓ 2 runtime-verified2026-10-09
https://github.com/acdsh4869/dsh-DeepSeek-chat
✓dsh 0.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/acdsh4869/dsh-DeepSeek-chat#v1.0.0
ID: dsh-deepseek-chat-6@v1.0.0@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: github · https://github.com/acdsh4869/dsh-DeepSeek-chat#v1.0.0
ID: dsh-deepseek-chat-6@v1.0.0@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.
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-deepseek-chat-6/?ref=badge)``[](https://www.dsh.so/artifact/dsh-deepseek-chat-6/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-deepseek-chat-6/?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 low; dynamic medium (authoritative when present) → overall medium.
v1.0.0dsh manifestv1.0.0git2026-10-09v2.0.0version moved onclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningchildProcess · code-exec
index.js:453const ps = spawn( - warningchildProcess · code-exec
index.js:510const ps = spawn( - warningchildProcess · code-exec
index.js:688const child = spawn(found.exe, args, { - warningnetIp · network
index.js:567const r = await fetch('http://127.0.0.1:' + port + '/json/version', { signal: ctrl.signal }) - warningnetIp · network
index.js:1002const r = await fetch('http://127.0.0.1:' + port + '/json/list') - warningnetIp · network
index.js:1473const u = new URL(String(req.url || ''), 'http://127.0.0.1') - warningfsWrite · files
index.js:1677fs.writeFileSync(
show 3 audit findings
- mediumRelay mode is on by default and opens an unauthenticated CDP port, giving any local process control of the logged-in DeepSeek window
index.js:679With DEFAULTS.relay = true, every launch adds --remote-debugging-port on 127.0.0.1. Chrome's DevTools endpoint has no authentication, and the window uses a persistent profile that stores chat.deepseek.com session cookies (the whole point of the plugin). Any other process on the machine — including a different local Windows user, since loopback ports are not per-user isolated — can call /json/list and attach, then Runtime.evaluate inside the authenticated page to read conversations, localStorage and metadata, or send messages as the user. The bundled page-script adds no protection because the a
- low/status route skips the trust fence, so any web origin can overwrite the fixed temp diagnostic file
index.js:1741Because opts.raw is true, rejection() is never applied to POST /dsh-deepseek-chat/status. A simple cross-origin form/text-plain POST from any website the user visits reaches the handler (no preflight needed) and rewrites %TEMP%/dsh-deepseek-chat-status.json with up to 32 KB of attacker-chosen JSON. No data is returned and the path is not attacker-controlled, so this is integrity-only: whoever reads the diagnostic file (support workflows, tooling, the user) can be fed spoofed browser paths, profile paths or phase records.
- lowSynthetic Alt keystroke is injected to defeat the Windows foreground lock
index.js:870focusDshWindow/focusWindowByPids fake a user key press so SetForegroundWindow succeeds. This is real input injection at the OS level: it can steal focus away from whatever the user is doing, and a synthetic Alt press may activate the menu bar of the currently focused application. It runs automatically whenever a relay item arrives (onBindingCalled → focusDshWindow), i.e. triggered by page content the user selected, not only by an explicit click.
Scanner warnings are mostly benign fixed-argument PowerShell/spawn usage; the real issues are a default-on unauthenticated CDP port and a fence-bypassing status route.
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-10 · activity: Stable
• Repo created: 2026-09-29
• Stars: ★ 2 · 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 @acdsh4869/dsh-DeepSeek-chat?
@acdsh4869/dsh-DeepSeek-chat 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 @acdsh4869/dsh-DeepSeek-chat?
Run dsh plugin --profile web add github:acdsh4869/dsh-DeepSeek-chat#v1.0.0 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-10-31 (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.