⚠️ This repository has been renamed: RUO-MO/DSH-Plugin — click to visit the new location. Everything below is preserved as originally indexed.
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
Embeds the chat.deepseek.com web chat in the DSH sidebar with no API key and no DSH session token usage, on Web and Electron.
- Embeds chat.deepseek.com web chat right in the sidebar
- No API Key required to start chatting
- Does not consume DSH session tokens
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:RUO-MO/dsh-deepseek-webInstall method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.0-rc.2
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.0-rc.2 | dsh 0.2.0-rc.1 | dsh 0.1.7-rc.2 | dsh 0.1.7-rc.1 | dsh 0.1.7-alpha.1 |
|---|---|---|---|---|---|
| 6264de | ○ | ○ | ○ | ○ | ○ |
6264degithub✓ 1 runtime-verified○ 8 ecosystem plugin2026-10-09
https://github.com/RUO-MO/dsh-deepseek-web
○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/RUO-MO/dsh-deepseek-web (version unstated)
ID: dsh-deepseek-web-4@6264de@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.2.0-rc.12026-09-30Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/RUO-MO/dsh-deepseek-web (version unstated)
ID: dsh-deepseek-web-4@6264de@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-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.1.7-rc.22026-09-28Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/RUO-MO/dsh-deepseek-web (version unstated)
ID: dsh-deepseek-web-4@6264de@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-28 · expires: 2026-10-05
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-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/RUO-MO/dsh-deepseek-web (version unstated)
ID: dsh-deepseek-web-4@6264de@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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-alpha.12026-09-22Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.1
- • Plugin artifact: github · https://github.com/RUO-MO/dsh-deepseek-web (version unstated)
ID: dsh-deepseek-web-4@6264de@dsh0.1.7-alpha.1 · profile: l4-sandbox
Issued: 2026-09-22 · expires: 2026-09-29
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.22026-09-21Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/RUO-MO/dsh-deepseek-web (version unstated)
ID: dsh-deepseek-web-4@6264de@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-21 · expires: 2026-09-28
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/RUO-MO/dsh-deepseek-web (version unstated)
ID: dsh-deepseek-web-4@6264de@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.
✓dsh 0.1.5-rc.22026-09-14L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/RUO-MO/dsh-deepseek-web (version unstated)
ID: dsh-deepseek-web-4@6264de@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-14 · expires: 2026-09-21
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-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/RUO-MO/dsh-deepseek-web (version unstated)
ID: dsh-deepseek-web-4@6264de@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-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.
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-web-4/?ref=badge)``[](https://www.dsh.so/artifact/dsh-deepseek-web-4/?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.
—595762592ab3git2026-10-08595762592ab3same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningnetIp · network
plugin/dsh-deepseek-web/lib/client.js:75const base = `http://127.0.0.1:${PROBE_BASE_PORT + offset}`; - warningnetIp · network
plugin/dsh-deepseek-web/lib/index.js:420log.info(`deepseek-web: loopback proxy ready at http://127.0.0.1:${port} (upstream ${chatOrigin}, panel start ${config.startPath})`) - warningnetIp · network
plugin/dsh-deepseek-web/scripts/smoke-proxy.mjs:33const ping = await fetch('http://127.0.0.1:3899/dsh-deepseek-web/ping') - warningnetIp · network
plugin/dsh-deepseek-web/scripts/smoke-proxy.mjs:38const answer = await fetch(`http://127.0.0.1:3899${startPath}`, { headers: browserHeaders }) - warningnetIp · network
plugin/token-usage/lib/client.js:186let USAGE_URL = "http://127.0.0.1:47820/api/usage";
show 3 audit findings
- mediumLoopback usage endpoint replies with Access-Control-Allow-Origin: * exposing private token stats to any website
plugin/token-usage/lib/index.js:228The bridge is on by default (127.0.0.1:47820) and marks every /api/usage response readable by any origin. Any web page the user visits can fetch http://127.0.0.1:47820/api/usage and read per-model token counts, daily/hourly usage history and turn counts. It is a concrete out-of-band information-disclosure channel (subject to PNA in some Chromium builds, but open in many browsers).
- lowProxy rewrites upstream cookies onto loopback origin without Secure, exposing the session cookie to other 127.0.0.1 services
plugin/dsh-deepseek-web/lib/index.js:127Cookies are host-scoped (port-agnostic), so the DeepSeek auth cookie set on 127.0.0.1:3838 is sent to every port on 127.0.0.1. Another local service or a malicious plugin that binds a loopback port can receive the session cookie if the user browses to it. The sensitive asset is the DeepSeek session token; impact requires a local malicious component.
- lowProxy strips CSP/X-Frame-Options/COOP/COEP and rewrites Origin/Referer, weakening upstream protections
plugin/dsh-deepseek-web/lib/index.js:71Stripping framing/isolation headers is the plugin's purpose, but it also disables CSP/XFO/COOP/COEP for the proxied third-party page, and headers.origin/referer are rewritten to the upstream origin, bypassing DeepSeek's own CSRF header checks. Residual risk is limited on loopback because rewritten cookies are SameSite=Lax (not sent on cross-site subrequests) and the CORS response is not credentialed.
Loopback token-usage bridge answers with Access-Control-Allow-Origin: * so any website can read private usage stats; the DeepSeek proxy also writes the session cookie onto port-agnostic 127.0.0.1.
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-15 · activity: Stable
• Repo created: 2026-09-13
• Stars: ★ 3 · 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-deepseek-web?
dsh-deepseek-web 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 dsh-deepseek-web?
Run dsh plugin --profile web add github:RUO-MO/dsh-deepseek-web 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-10-21 (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.