This repository has been renamed: dsh-plugin-lab/dsh-workbuddy-bridge — click to visit the new location. Everything below is preserved as originally indexed.
Install verification: sandbox install ok, web smoke failed (L5) · tested on dsh 0.2.1-alpha.2 · last checked Install verification details →
Data as of (UTC)
What it doesAI
Bridges WorkBuddy desktop app models into DeepSeek Harness so they can be used directly in DSH chat with zero configuration.
- Connects WorkBuddy desktop app models into DeepSeek Harness
- Zero-configuration setup, use models directly in DSH chat
- Native panel in Settings > Plugins > Plugin config; TypeScript + CI, MIT
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-11) · 2 samples (roughly every 11 days), 2 of them reconstructed (hollow dots); sampled points, not a daily series
Only 2 points (< 3): no chart yet
09-25 → 10-06 · 2 points
Each bar = the delta between two samples 5–14 days apart; negative bars point down. Faint bars include reconstructed points
Only 1 points (< 3): no chart yet
10-06 → 10-06 · 1 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)
09-26 → 10-09 · 13 points
Installation
dsh plugin --profile web add dsh-workbuddy-bridgeInstall method: npm · sandbox install ok, web smoke failed (L5) · verified on dsh 0.2.1-alpha.2
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 a single engines.dsh range (decides alone; peerDependencies is not consulted). raw ranges
>=0.1.7-rc.2
✓ Running dsh 0.2.2-rc.1 is within the declared range — install is not blocked by version.
Deciding channel: since 0.2.1-alpha.4 DSH judges by engines.dsh when declared — peerDependencies is then not consulted.
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| plugin ＼ dsh | dsh 0.2.1-alpha.2 | dsh 0.2.0-rc.2 | dsh 0.2.0-rc.1 | dsh 0.1.7-rc.2 | prehistory |
|---|---|---|---|---|---|
| 0.3.1 | ✗ | ✗ | · | · | ✗ |
| 0.3.0 | · | · | · | · | ✗ |
| 0.2.0 | · | · | ✗ | · | ✗ |
| 0.1.0 | · | · | · | ✗ | · |
0.3.1npm3 failed2026-10-11
dsh-workbuddy-bridge
✗dsh 0.2.1-alpha.22026-10-11L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-workbuddy-bridge@0.3.1
ID: dsh-workbuddy-bridge@0.3.1@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-11 · expires: 2026-10-18
View checks & evidence
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: npm · dsh-workbuddy-bridge@0.3.1
ID: dsh-workbuddy-bridge@0.3.1@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-05L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-workbuddy-bridge@0.3.1
ID: dsh-workbuddy-bridge@0.3.1@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.3.0npm1 failed2026-10-04
dsh-workbuddy-bridge
✗prehistory2026-10-04L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-workbuddy-bridge@0.3.0
ID: dsh-workbuddy-bridge@0.3.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.2.0npm2 failed2026-10-03
dsh-workbuddy-bridge
✗dsh 0.2.0-rc.12026-09-30L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-workbuddy-bridge@0.2.0
ID: dsh-workbuddy-bridge@0.2.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-30 · expires: 2026-10-07
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
✗prehistory2026-10-03L5 · failed
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-workbuddy-bridge@0.2.0
ID: dsh-workbuddy-bridge@0.2.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-03 · expires: 2026-10-10
View checks & evidence
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
0.1.0npm1 failed2026-09-26
dsh-workbuddy-bridge
✗dsh 0.1.7-rc.22026-09-26L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-workbuddy-bridge@0.1.0
ID: dsh-workbuddy-bridge@0.1.0@dsh0.1.7-rc.2 · profile: l3-fullscan
Issued: 2026-09-26 · expires: 2026-10-03
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 dsh.so badges in your README to show this plugin's automated security-scan and install-test status:
`[](https://www.dsh.so/artifact/dsh-workbuddy-bridge/?ref=badge)`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.3.1dsh manifest0.3.1npm2026-10-10v0.5.7version moved onclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningshellExec · shell
lib/heartbeat-DihKwwFX.js:1954execFile(REG_BIN, [ - warningshellExec · shell
lib/heartbeat-DihKwwFX.js:1994const child = execFile(bin, [...args], { - warningshellExec · shell
lib/heartbeat-DihKwwFX.js:2281execFile(electronPath, [HELPER_SCRIPT_ARGUMENT_FLAG, HELPER_SCRIPT], { - warningnetIp · network
lib/index.js:770return `http://127.0.0.1:${address.port}`; - warningnetIp · network
lib/index.js:1615json$1(res, 200, workBuddySessionCredits(deps, new URL(req.url ?? "/", "http://127.0.0.1").searchParams.get("sessionId") ?? ""));
show 3 audit findings
- mediumDesktop credential key is derived by spawning a WorkBuddy binary located via Spotlight, with no evidenced integrity check
scripts/issue-48-forced-fallback-e2e.mjs:6When the default /Applications path fails, the plugin's key provider searches the filesystem with mdfind, picks the first WorkBuddy.app/Contents/MacOS/Electron it finds, executes it as a helper, and sends it the credential envelope key ids in exchange for the at-rest decryption key. No code-signature or bundle-identifier verification of that binary is evidenced anywhere in the harvested code. A planted application in any Spotlight-indexed, user-writable location would be executed by the plugin and would receive the key-derivation request, yielding the user's WorkBuddy tokens.
- lowDesktop OAuth tokens are copied verbatim into plugin-owned files under $DSH_HOME
src/variants.ts:71The plugin keeps its own plaintext copy of the WorkBuddy credential (.workbuddy-auth.json / .workbuddy-ai-auth.json) in addition to the desktop app's store, and the developer e2e script writes yet another copy to ~/.dsh/.workbuddy-e2e-check.json. Each copy widens the window in which an access/refresh token sits at rest; the writer's file mode is not visible in this harvest, so 0600 permissions cannot be confirmed.
- lowOrigin gate passes any request without an Origin header, leaving only the bearer secret for non-browser local clients
src/llm/loopback.ts:43This is intentional (the plugin's own fetch calls send no Origin), but it means the browser-CSRF defense does not apply to a local process that omits Origin; such a process only has to learn the loopback port and the in-memory bearer token. scripts/verify-shim-hardening.mjs shows the bearer gate is enforced (401 without it), so this is a defense-in-depth gap rather than an open door.
Local LLM bridge that reuses the WorkBuddy desktop credential; loopback guards look solid, but credential extraction via a Spotlight-discovered helper and plaintext token copies are residual risks.
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-11-08 · activity: Active
• Repo created: 2026-09-25
• Stars: ★ 35 · Forks: 7
• 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).
Frequently asked questions
What is @zlZayn/dsh-workbuddy-bridge?
@zlZayn/dsh-workbuddy-bridge 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 @zlZayn/dsh-workbuddy-bridge?
Run dsh plugin --profile web add dsh-workbuddy-bridge in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4); the web smoke test (L5) has not passed 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.