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
DSH plugin merging WorkBuddy, Trae and Qoder model channels into one model picker with a unified status panel, check-in and channel management.
- WorkBuddy / Trae / Qoder models side by side in one model picker
- Status panel shows login, quota, check-in state and model count
- One-click daily check-in plus add, rename, disable or delete channels
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.
current (registry 2026-11-10) · 7 samples (roughly every 7 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
09-25 → 11-07 · 7 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
10-06 → 11-07 · 5 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:yembors64632/dsh-connectInstall method: GitHub · 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 7 @deepseek-ai/dsh-* packages. raw ranges
^0.1.5-rc.1 || ^0.1.6-alpha.1 || ^0.1.7-alpha.1 ×7
✗ 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-3@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 |
|---|---|---|---|---|---|
| 240e45 | ✗ | ✗ | ✗ | ✗ | ✗ |
240e45github✓ 1 runtime-verified7 failed2026-11-04
https://github.com/yembors64632/dsh-connect
✗dsh 0.2.1-rc.52026-10-31L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/yembors64632/dsh-connect (version unstated)
ID: dsh-connect-3@240e45@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-10-31 · expires: 2026-11-07
View checks & evidence
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
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.2.1-rc.32026-10-26L4 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/yembors64632/dsh-connect (version unstated)
ID: dsh-connect-3@240e45@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-26 · expires: 2026-11-02
View checks & evidence
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
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.2.1-rc.22026-10-19L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/yembors64632/dsh-connect (version unstated)
ID: dsh-connect-3@240e45@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
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-16L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/yembors64632/dsh-connect (version unstated)
ID: dsh-connect-3@240e45@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
View checks & evidence
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
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-12L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/yembors64632/dsh-connect (version unstated)
ID: dsh-connect-3@240e45@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
View checks & evidence
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
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-09L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/yembors64632/dsh-connect (version unstated)
ID: dsh-connect-3@240e45@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
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: github · https://github.com/yembors64632/dsh-connect (version unstated)
ID: dsh-connect-3@240e45@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@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-09-30L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/yembors64632/dsh-connect (version unstated)
ID: dsh-connect-3@240e45@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
↳ carried from earlier record dsh-connect-3@240e45@dsh0.2.2-rc.1 (l3-fullscan)
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-connect-3/?ref=badge)``[](https://www.dsh.so/artifact/dsh-connect-3/?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 low (authoritative when present) → overall low.
v0.2.0dsh manifest0.2.0git2026-11-110.2.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- warningnetIp · network
scripts/connect-status.mjs:9const ORIGIN = "http://127.0.0.1:3080"; - warningnetIp · network
scripts/connect-status.mjs:10const BASE = process.env.DSH_BASE ?? "http://127.0.0.1:3088"; - warningnetIp · network
scripts/export-connect-credentials.mjs:305['exec', CONTAINER, 'curl', '-s', '--max-time', '60', `http://127.0.0.1:${PORT}/plugins/dsh-connect/status`], - warningnetIp · network
scripts/wb-login.mjs:22const base = argOf('--base', process.env.WB_BASE ?? 'http://127.0.0.1:3088').replace(/\/$/, '');
show 3 audit findings
- lowrestore extracts an arbitrary user-supplied tarball into ~/.dsh/connect-auth without validating entry paths
scripts/export-connect-credentials.mjs:277Archive entries using ../ or absolute paths are extracted with the invoking user's privileges, so a hostile archive can overwrite files outside AUTH_DIR (path traversal). Precondition: the operator explicitly runs 'restore --bundle <hostile.tar.gz>'; no remote attacker reaches this code.
- lowQoder PAT is accepted as a command-line argument and persisted in plaintext
scripts/export-connect-credentials.mjs:175The PAT is captured from argv, so it appears in shell history and in the process list while the script runs; the persisted file is a plaintext long-lived credential (0600 only).
- lowbundle writes a plaintext credentials tarball into the repository working directory by default
scripts/export-connect-credentials.mjs:247All five channel tokens/sessions are packaged unencrypted into a file inside the project tree, where it can be picked up by git add -A, editor indexing, or backup tooling. The script does print a warning, so this is a hygiene gap rather than an undisclosed channel.
Visible runtime code has no exploitable path; only low-severity hygiene issues in host-side credential-export scripts. Panel/provider sources were not in the harvest.
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-28 · activity: Stable
• Repo created: 2026-09-25
• Stars: ★ 17 · Forks: 3
• 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 @yembors64632/dsh-connect?
@yembors64632/dsh-connect 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 @yembors64632/dsh-connect?
Run dsh plugin --profile web add github:yembors64632/dsh-connect 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-11 (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.