Install verification: sandbox install failed (L4) · tested on dsh 0.2.1-rc.5 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Bridges already-logged-in local Qoder and Qoder CN models into DeepSeek Harness so their quota shows up in DSH's model picker.
- Adds local Qoder / Qoder CN as zero-config DSH model providers
- Implements COSY signing headers, permuted base64 bodies and double-layer SSE
- Qoder CN and Qoder run side by side with separate accounts and quotas
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.
6 samples (roughly every 7 days), 3 of them reconstructed (hollow dots); sampled points, not a daily series
09-21 → 10-29 · 6 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-06 → 10-29 · 4 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-21 → 11-03 · 41 points
The snapshot’s last-week rolling window (official npm + npmmirror combined)
09-21 → 11-04 · 42 points
Installation
dsh plugin --profile web add dsh-connect-qoderInstall method: npm · sandbox install failed (L4) · verified on dsh 0.2.1-rc.5
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
Based on 1 requirement(s) across 8 @deepseek-ai/dsh-* packages. raw ranges
0.1.0-rc.6 || 0.1.2-rc.1 || >=0.1.5-0 <0.2.0-0 || 0.1.6-alpha.1 || 0.1.6-alpha.2 ×8
✗ Running dsh 0.2.2-rc.1 is outside the declared range — the official install gate rejects it (incompatible-version).
To force-install, grant an exact-version exemption: dsh plugin allow-version dsh-connect-qoder@0.2.0 0.2.2-rc.1 (the exemption lives in the local profile; this site does not assume one)
Deciding channel: no engines.dsh declared, so every dsh* peer is checked (workspace:^ | ~ | * counts as the running version).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|---|---|
| 0.2.0 | · | · | ✓ | ✓ | ✓ |
| 0.1.1 | · | · | · | · | · |
| v0.1.0 | · | · | · | · | · |
0.2.0npm✓ 7 runtime-verified2026-11-04
dsh-connect-qoder
✓dsh 0.2.1-rc.22026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-connect-qoder@0.2.0
ID: dsh-connect-qoder@0.2.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
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-15L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-connect-qoder@0.2.0
ID: dsh-connect-qoder@0.2.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-15 · expires: 2026-10-22
View checks & evidence
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
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-10L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-connect-qoder@0.2.0
ID: dsh-connect-qoder@0.2.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-10 · expires: 2026-10-17
View checks & evidence
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
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-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · dsh-connect-qoder@0.2.0
ID: dsh-connect-qoder@0.2.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-08 · expires: 2026-10-15
View checks & evidence
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
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.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-connect-qoder@0.2.0
ID: dsh-connect-qoder@0.2.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
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-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-connect-qoder@0.2.0
ID: dsh-connect-qoder@0.2.0@dsh0.1.7-rc.2 · profile: l3-fullscan
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
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-connect-qoder@0.2.0
ID: dsh-connect-qoder@0.2.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.1npm✓ 1 runtime-verified2026-09-20
dsh-connect-qoder
✓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-connect-qoder@0.1.1
ID: dsh-connect-qoder@0.1.1@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-qoder@0.2.0@dsh0.2.2-rc.1 (l3-fullscan)
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
v0.1.0github2026-09-20
https://github.com/hdhgsysh/dsh-connect-qoder
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
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-connect-qoder/?ref=badge)``[](https://www.dsh.so/artifact/dsh-connect-qoder/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-connect-qoder/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-connect-qoder/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-connect-qoder/?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.
v0.2.0dsh manifest0.2.0npm2026-11-050.2.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningshellExec · shell
lib/credentials.js:126execFileSync( - warningbase64Decode · obfuscation
lib/credentials.js:102$raw = [Convert]::FromBase64String($json.os_crypt.encrypted_key) - warningnetIp · network
lib/index.js:573const force = new URL(req.url ?? '/', 'http://127.0.0.1').searchParams.get('refresh') === '1' - warningnetIp · network
lib/index.js:651const force = new URL(req.url ?? '/', 'http://127.0.0.1').searchParams.get('refresh') === '1' - warningnetIp · network
lib/shim.js:116return `http://127.0.0.1:${address.port}`
show 3 audit findings
- mediumDecrypts another application's OS-keystore-protected Qoder tokens (access + refresh) and keeps them in memory
lib/credentials.js:104This is the plugin's stated design, but the effect is that any process hosting this module obtains the full Qoder sign-in session (token + refreshToken from auth.v1.dat / secret://aicoding.auth.userInfo) of a different vendor application, and holds it for the lifetime of the DSH process. A compromised harness, a sibling plugin able to reach this module state or the same user's DPAPI scope, or a core dump/log inherits durable account access; the DPAPI-unwrap primitive itself generalises to any Chromium OSCrypt secret stored for the same user.
- lowLoopback card routes accept requests with no Origin header and have no authentication
lib/index.js:142Any local process (or a top-level browser navigation, which sends no Origin) can GET /plugins/dsh-connect-qoder/models and /usage and read model metadata and account quota figures, and can pass ?refresh=1 to make the host issue authenticated upstream Qoder requests. No credential is returned, and the shim itself is unaffected (it separately requires a random bearer token).
- lowSpawns powershell.exe and stages the DPAPI-unwrapped AES key in a temp file
lib/credentials.js:126The command line is a constant script with values passed via environment, so there is no command or argument injection; the child process only runs when a 'Local State' file exists. Residual risk is the capability itself: a PowerShell child process is spawned and the unwrapped Oscrypt key is written to a temp directory before being read and deleted, giving any same-user process a short window to open that file (though such a process could call DPAPI directly anyway).
Reads/decrypts Qoder desktop tokens via DPAPI+OSCrypt and proxies them through a token-guarded loopback shim; residual risk is long-lived credentials and origin-only loopback routes.
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-09-19
• Stars: ★ 23 · Forks: 9
• 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 @hdhgsysh/dsh-connect-qoder?
@hdhgsysh/dsh-connect-qoder 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 @hdhgsysh/dsh-connect-qoder?
Run dsh plugin --profile web add dsh-connect-qoder in a DeepSeek Harness (dsh) environment. The command is parsed from the plugin manifest and its install spec is verified (L3); runtime sandbox install testing may not have run yet.
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-05 (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.