Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs.Install verification details →
Data as of (UTC)
What it doesAI
A plugin bridging OpenAI-compatible APIs and pi-ai provider into DeepSeek Harness for agent workflows.
- Provides OpenAI-compatible API bridge
- Adds pi-ai provider support
- Enables agent integration 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 github:aybrt/workbuddy-dsh-plugin#v1.0.0Install method: GitHub · runtime test inconclusive (L5 unknown)
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, so one plugin is re-read roughly every 5–14 days, sparser than npm; the npm pair has a value on every snapshot day. The two cumulative panels are smoothed curves with no sample markers; the two weekly panels keep their raw bars and add a 4-week moving-average trend line that strips single-week noise down to the direction of travel.
8 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-17 → 11-08 · 8 points
Bars = the delta between two samples 5–14 days apart (negative points down, faint bars contain reconstructed points); line = 4-week moving-average trend
09-24 → 11-08 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
Bars = the snapshot’s last-week rolling window (official npm + npmmirror combined); line = 4-week moving-average trend — the shape of weekly demand, not a user count
Only 0 points (< 3): no chart yet
no data yet
Verification & Compatibility○ Ecosystem plugin
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
package manifest not collected — the declared range is unknown.
| plugin \ dsh | dsh 0.2.2-rc.3 current | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| v1.0.0 | ○ | ○ | ○ | ○ | ○ |
v1.0.0github○ 18 ecosystem plugin2026-11-17
https://github.com/aybrt/workbuddy-dsh-plugin
○dsh 0.2.2-rc.3current2026-11-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-17 · expires: 2026-11-24
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.2-rc.12026-11-06Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.1-rc.52026-11-01Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
View checks & evidence
not present in web-profile loader inventory
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-27Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
View checks & evidence
not present in web-profile loader inventory
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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-27
View checks & evidence
not present in web-profile loader inventory
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-18Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
View checks & evidence
not present in web-profile loader inventory
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-12Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
View checks & evidence
not present in web-profile loader inventory
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-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
not present in web-profile loader inventory
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-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
not present in web-profile loader inventory
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-25Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-25 · expires: 2026-10-02
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.7-alpha.22026-09-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
not present in web-profile loader inventory
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-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
not present in web-profile loader inventory
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-17Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.5-rc.22026-09-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
not present in web-profile loader inventory
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-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
not present in web-profile loader inventory
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-07Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.2-rc.12026-09-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-05Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/aybrt/workbuddy-dsh-plugin#v1.0.0
ID: workbuddy-dsh-plugin@v1.0.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
View checks & evidence
not present in web-profile loader inventory
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/workbuddy-dsh-plugin/?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.
—v1.0.0git2026-11-17v1.0.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (11)
- warningchildProcess · code-exec
bridge/server.js:281const child = spawn(process.execPath, [CLI, ...args], { - warningnetIp · network
bridge/server.js:435const url = new URL(req.url, `http://127.0.0.1:${PORT}`); - warningnetIp · network
bridge/server.js:451console.log(`[bridge] WorkBuddy agent 桥接就绪: http://127.0.0.1:${PORT}/v1`); - warningnetIp · network
bridge/server.js:454console.log("[bridge] DSH 配置: baseUrl=http://127.0.0.1:" + PORT + "/v1 apiKey=任意占位(桥接复用 WorkBuddy 登录态)"); - warningnetIp · network
install.mjs:27const BRIDGE_BASE = `http://127.0.0.1:${PORT}/v1`; - warningchildProcess · code-exec
manager.mjs:75const r = spawnSync("powershell", PS_KILL, { encoding: "utf8", windowsHide: true, timeout: 30000 }); - warningchildProcess · code-exec
manager.mjs:82const r = spawnSync("powershell", PS_KILL_MANAGERS, { encoding: "utf8", windowsHide: true, timeout: 30000 }); - warningchildProcess · code-exec
manager.mjs:105const r = spawnSync(process.execPath, [INSTALLER], { - warningnetIp · network
manager.mjs:138const h = await fetch(`http://127.0.0.1:${port}/health`, { signal: AbortSignal.timeout(3000) }); - warningnetIp · network
manager.mjs:141const m = await (await fetch(`http://127.0.0.1:${port}/v1/models`, { signal: AbortSignal.timeout(3000) })).json(); - warningnetIp · network
manager.mjs:173log(`READY: http://127.0.0.1:${port}/v1`);
show 6 audit findings
- mediumUnauthenticated loopback bridge accepts any web origin (Access-Control-Allow-Origin: *)
bridge/server.js:50Every response (including /v1/chat/completions) carries a wildcard CORS header while no token/Origin check exists anywhere in the file. A malicious page the user visits can send a CORS-simple POST (Content-Type: text/plain, JSON body) to http://127.0.0.1:8096/v1/chat/completions and read the answer; the prompt is handed to codebuddy.js with the default read-only whitelist (Read,Grep,Glob), so a crafted prompt can make the local agent read files and return their contents, and can consume the user's WorkBuddy quota.
- lowInstaller silently discards the existing llm-pi-ai section of ~/.dsh/settings.yaml
install.mjs:155The whole llm-pi-ai block (all its indented lines, including providers the user configured) is replaced by a section that only defines the 'workbuddy' provider, without backup and without asking. Other configured providers/models under that key are lost.
- lowInstaller writes a fixed key value into the user's DSH credential store
install.mjs:140The installer edits ~/.dsh/.credentials.yaml (credFile, line 128) and inserts/replaces WORKBUDDY_API_KEY with the static constant 'wb-dsh-bridge-key'. The value is a placeholder, not a leaked secret, but a plugin is modifying the user's credential store outside its own directory without explicit consent.
- lowSingle-instance lock force-kills node processes matched by loose PowerShell command-line patterns
manager.mjs:47killOtherManagers() runs this via spawnSync('powershell', ...) on every start and unconditionally kills any node.exe whose command line merely contains 'manager.mjs' (and no 'node_modules'). An unrelated user script with that file name, or a process that received it as an argument, is terminated with -Force; the sibling pattern for bridges ('*workbuddy-plugin*bridge*server.js*') is similarly substring-based.
- lowBridge strips refusal/error history and injects a 'never refuse' system prompt
bridge/server.js:92cleanMessages() prepends this system instruction and cleanHistory() deletes assistant messages matching /本轮运行失败|PI_AI_ERROR|抱歉,系统检测|无法响应|敏感内容|No API key/i before forwarding to the agent. This is deliberate steering of the downstream model's safety/error behavior and hides CLI failures from the user; it also means the bridge actively suppresses refusal text that DSH would otherwise surface.
- lowHardcoded developer absolute paths used as default install targets
install.mjs:24Defaults embed the author's username (also in INSTALL_DIR, line 23) and the installer creates and writes into that absolute path (mkdirSync + writeFileSync of workbuddy.json under node_modules/@earendil-works/pi-ai/dist/providers/data), i.e. it mutates an installed npm package outside the plugin directory; on other machines this either fails or attempts to create directories under C:\Users\<author>.
Loopback WorkBuddy/OpenAI bridge has wildcard CORS and no auth (browser-reachable local agent), plus an installer/manager that force-kills node processes and rewrites DSH config and credential files.
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-08-16 · activity: Inactive
• Repo created: 2026-08-16
• Stars: ★ 3 · Forks: 1
• Health: Inactive — no commit in 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 workbuddy-dsh-plugin?
workbuddy-dsh-plugin is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly.
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 workbuddy-dsh-plugin?
Run dsh plugin --profile web add github:aybrt/workbuddy-dsh-plugin#v1.0.0 in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs.
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-17 (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.
