Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Connects ChatGPT models to DeepSeek Harness through the Codex app-server.
- ChatGPT model connector for DSH
- Powered by Codex app-server
- Integrates with DeepSeek Harness
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 @canary-builds/dsh-connectInstall method: npm · runtime verified (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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 |
|---|---|---|---|---|---|
| 0.4.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
| 0.3.3 | · | · | · | · | · |
| v0.3.3 | · | · | · | · | · |
0.4.0npm✓ 6 runtime-verified2026-10-19
@canary-builds/dsh-connect
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @canary-builds/dsh-connect@0.4.0
ID: dhs-connect@0.4.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
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.
✓dsh 0.2.1-alpha.42026-10-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · @canary-builds/dsh-connect@0.4.0
ID: dhs-connect@0.4.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-17 · expires: 2026-10-24
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.
✓dsh 0.2.1-alpha.22026-10-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · @canary-builds/dsh-connect@0.4.0
ID: dhs-connect@0.4.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
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.
✓dsh 0.2.0-rc.22026-10-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: npm · @canary-builds/dsh-connect@0.4.0
ID: dhs-connect@0.4.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.
✓dsh 0.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · @canary-builds/dsh-connect@0.4.0
ID: dhs-connect@0.4.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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: npm · @canary-builds/dsh-connect@0.4.0
ID: dhs-connect@0.4.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.
0.3.3npm✓ 4 runtime-verified2026-09-25
@canary-builds/dsh-connect
✓dsh 0.1.7-rc.22026-09-25L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · @canary-builds/dsh-connect@0.3.3
ID: dhs-connect@0.3.3@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
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.
✓dsh 0.1.7-rc.12026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · @canary-builds/dsh-connect@0.3.3
ID: dhs-connect@0.3.3@dsh0.1.7-rc.1 · profile: l3-fullscan
Issued: 2026-09-23 · expires: 2026-09-30
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.
✓dsh 0.1.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: npm · @canary-builds/dsh-connect@0.3.3
ID: dhs-connect@0.3.3@dsh0.1.6-alpha.2 · profile: l4-sandbox
Issued: 2026-09-20 · expires: 2026-09-27
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.
✓dsh 0.1.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: npm · @canary-builds/dsh-connect@0.3.3
ID: dhs-connect@0.3.3@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.
v0.3.3github✓ 3 runtime-verified2026-09-11
https://github.com/Canary-Builds/dhs-connect
✓dsh 0.1.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/Canary-Builds/dhs-connect#v0.3.3
ID: dhs-connect@v0.3.3@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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.
✓dsh 0.1.3-alpha.22026-09-08L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/Canary-Builds/dhs-connect#v0.3.3
ID: dhs-connect@v0.3.3@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
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.
✓dsh 0.1.3-alpha.12026-09-07L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/Canary-Builds/dhs-connect#v0.3.3
ID: dhs-connect@v0.3.3@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
active in loader tree (151 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 official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dhs-connect/)``[](https://www.dsh.so/artifact/dhs-connect/)``[](https://www.dsh.so/artifact/dhs-connect/)``[](https://www.dsh.so/artifact/dhs-connect/)``[](https://www.dsh.so/artifact/dhs-connect/)``[](https://www.dsh.so/artifact/dhs-connect/)``[](https://www.dsh.so/artifact/dhs-connect/)`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.4.0dsh manifest0.4.0npm2026-10-210.4.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (7)
- warningchildProcess · code-exec
src/grok-device.js:27const child = spawn(launch.command, ['login', '--device-auth'], { env: launch.env, stdio: ['ignore', 'pipe', 'pipe'] }); - warningchildProcess · code-exec
src/grok-device.js:69const child = spawn(launch.command, ['logout'], { env: launch.env, stdio: 'ignore' }); - warningchildProcess · code-exec
src/grok-login.js:11const child = spawn(launch.command, ['login', ...(args.length ? args : ['--device-auth'])], { env: launch.env, stdio: 'inherit' }); - warningchildProcess · code-exec
src/grok-transport.js:37const child = spawn(launch.command, launch.args, { cwd: launch.cwd, env: launch.env, stdio: ['pipe', 'pipe', 'pipe'] }); - warningchildProcessImport · code-exec
src/http.js:3import { execFile } from 'node:child_process'; - warningchildProcess · code-exec
src/login.js:11const child = spawn(launch.command, ['login', ...args], { env: launch.env, stdio: 'inherit' }); - warningchildProcess · code-exec
src/transport.js:65const child = spawn(launch.command, launch.args, { cwd: launch.cwd, env: launch.env, stdio: ['pipe', 'pipe', 'pipe'] });
show 1 audit findings
- lowRuntime imports adapter.js and grok-adapter.js, which are absent from the audited source
src/index.js:3index.js (line 3) and line 8 (`import { GrokAdapter } from './grok-adapter.js';`) load two modules that handle provider streaming and tool-call bridging but were not included in the 15 harvested files, so their behavior is unverified and the audit's clean verdict does not cover them.
Spawn-based provider bridge with a loopback-only settings API; command injection, CSRF and secret-leak paths are all guarded, so the static warnings are false positives except an audit-coverage gap.
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-09-25 · activity: Active
• Repo created: 2026-09-05
• Stars: ★ 0 · Forks: 1
• 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).
