Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Registers a zed-agent route in DSH so you can use your Zed AI (Pro/Student) subscription with Claude and GPT models.
- Adds a zed-agent route with Claude + GPT models
- Editable provider card on the Models page
- Includes a model chooser for quick switching
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 dsh-zed-providerInstall method: npm · sandbox install ok, web smoke failed (L5)
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 2 @deepseek-ai/dsh-* packages. raw ranges
0.2.1-alpha.2 ×2
✗ Running dsh 0.2.1-rc.2 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-zed-provider@0.1.2 0.2.1-rc.2 (the exemption lives in the local profile; this site does not assume one)
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 |
|---|---|---|---|
| 0.1.4 | ✗ | · | · |
| 0.1.3 | · | ✗ | · |
| 0.1.2 | · | · | ✗ |
0.1.4npm1 failed2026-10-21
dsh-zed-provider
✗dsh 0.2.1-rc.2current2026-10-21L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-zed-provider@0.1.4
ID: dsh-zed-provider@0.1.4@dsh0.2.1-rc.2 · profile: l3-fullscan
Issued: 2026-10-21 · expires: 2026-10-28
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.3npm1 failed2026-10-18
dsh-zed-provider
✗dsh 0.2.1-alpha.42026-10-18L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-zed-provider@0.1.3
ID: dsh-zed-provider@0.1.3@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.2npm1 failed2026-10-15
dsh-zed-provider
✗dsh 0.2.1-alpha.22026-10-14L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-zed-provider@0.1.2
ID: dsh-zed-provider@0.1.2@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-14 · expires: 2026-10-21
View checks & evidence
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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-zed-provider/)`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 — stricter wins → overall low.
v0.1.4dsh manifest0.1.4npm2026-10-210.1.4same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalshellExec · shell
lib/index.js:108function exec(file, args, timeout = 5000) { - criticalshellExec · shell
lib/index.js:120const secret = (await exec('security', ['find-generic-password', '-s', 'zed.dev', '-a', 'zed-credentials', '-w'])) ?? - warningshellExec · shell
lib/index.js:110execFile(file, args, { timeout }, (error, stdout) => resolve(error ? undefined : stdout)); - warningnetIp · network
lib/index.js:519const url = new URL(request.url ?? '/', 'http://127.0.0.1');
show 2 audit findings
- lowPlugin silently reads the Zed credential from the OS keyring during normal requests
lib/index.js:123When no config credential is present, zedCredential() falls back to importLocalZedCredential(), which reads a long-lived Zed access token from the macOS keychain / Linux secret-tool without an explicit per-action user gesture, then persists it via storeCredential. It is documented in the module header and is not sent to any third party, but it is an automatic secret-access capability the user may not expect.
- lowLoopback sign-in server has no origin/state check; any local request with ?error aborts sign-in
lib/index.js:525The server listens on a fixed, guessable loopback port (127.0.0.1:48921) and settles/fails on an unauthenticated query parameter. A malicious local page could hit http://127.0.0.1:48921/?error=... during a sign-in to abort it (low-impact DoS). Token injection is prevented because the access_token must decrypt with the freshly generated private key.
Legitimate Zed Cloud LLM provider; no injection or arbitrary exec on attacker input, credentials only travel to the configured Zed host. Two low-risk capabilities noted.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-17 · activity: Active
• Repo created: 2026-10-13
• Stars: ★ 1 · Forks: 0
• Health: Active — committed within last 30 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).