Install verification: runtime verified (L5) · tested on dsh 0.2.2-rc.3 · last checked Install verification details →
Showing badges for the 5 most recent dsh versions; older ones are hidden.
Data as of (UTC)
What it doesAI
Aggregates idle compute from multiple machines into a distributed AI compute pool for parallel Harness development and research.
- Pool idle compute from friends/LAN/cloud ECS
- Distributed AI compute pool for parallel tasks
- One person controls multiple Harness instances
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-fleetInstall method: npm · runtime verified (L5) · verified on dsh 0.2.2-rc.3
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.
9 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-21 → 11-18 · 9 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
10-06 → 11-18 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
08-22 → 11-17 · 74 points
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
08-22 → 11-18 · 75 points
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.2-rc.3 | dsh 0.2.2-rc.1 | dsh 0.2.1-rc.5 | dsh 0.2.1-rc.3 | dsh 0.2.1-rc.2 |
|---|---|---|---|---|---|
| 0.1.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
0.1.0npm✓ 17 runtime-verified2026-11-17
dsh-fleet
✓dsh 0.2.2-rc.32026-11-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dsh0.2.2-rc.3 · profile: l4-sandbox
Issued: 2026-11-17 · expires: 2026-11-24
View checks & evidence
active in loader tree (206 entries)
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-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-06 · expires: 2026-11-13
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-rc.52026-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dsh0.2.1-rc.5 · profile: l4-sandbox
Issued: 2026-11-01 · expires: 2026-11-08
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-rc.32026-10-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.3
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dsh0.2.1-rc.3 · profile: l4-sandbox
Issued: 2026-10-27 · expires: 2026-11-03
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-rc.22026-10-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-20 · expires: 2026-10-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.2.1-alpha.42026-10-18L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-18 · expires: 2026-10-25
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-12L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dsh0.2.1-alpha.2 · profile: l4-sandbox
Issued: 2026-10-12 · expires: 2026-10-19
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 · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.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.1.7-rc.22026-09-26L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
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-24L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
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 · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@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 · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@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.
✓dsh 0.1.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@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: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@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-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
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.
✓dsh 0.1.2-rc.12026-09-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
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-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-fleet@0.1.0
ID: dsh-fleet@0.1.0@dshunknown · profile: l4-sandbox
Issued: 2026-10-05 · expires: 2026-10-12
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.
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-fleet/?ref=badge)``[](https://www.dsh.so/artifact/dsh-fleet/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-fleet/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-fleet/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-fleet/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-fleet/?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 high (authoritative when present) → overall high.
v0.1.0dsh manifest0.1.0npm2026-11-190.1.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningnetIp · network
installer/install.sh:103log " · 监听端口 47900(被调用方);Web UI: http://127.0.0.1:3080" - warningcurlDownload · network
installer/install.sh:18curl -fsSL https://nodejs.org/dist/v24.11.1/node-v24.11.1-linux-x64.tar.xz -o /tmp/node.tar.xz - warningfsWrite · files
src/identity.js:32fs.writeFileSync(p, JSON.stringify(identity, null, 2), { encoding: 'utf8', mode: 0o600 }) - warningfsWrite · files
src/memberships.js:19fs.writeFileSync(filePath(home), JSON.stringify(data, null, 2)) - warningfsWrite · files
src/roster.js:22fs.writeFileSync(p, JSON.stringify(roster, null, 2)) - warningfsWrite · files
src/teams.js:24fs.writeFileSync(teamsPath(home), JSON.stringify(teams, null, 2))
show 6 audit findings
- highCleartext TCP task auth binds only taskId, so an in-path attacker can rewrite the prompt the worker executes
src/task-runner.js:34submit_task payloads (prompt, workspace, apiKey, preset, model) travel as plain JSON lines (protocol.js encode = JSON.stringify + '\n') while the integrity check only covers taskId. An attacker who is in path (ARP/DNS spoof on the advertised LAN use case, or any intermediate hop) can modify a live submit_task without touching taskId; the worker's comparison still succeeds and the attacker-chosen prompt runs in the worker harness with the mounted preset (bash/fs tools), i.e. code execution on the worker. Model keys and task results also cross the wire in clear.
- mediumPermanent worker SK is embedded in the copy-paste machine card with no expiry or rotation
src/card.js:8The onboarding flow is 'paste the card into the other machine', and the card carries the worker's long-lived SK, which is the sole capability for authenticating to the worker and submitting agent tasks (bash/fs). Anyone who ever sees the card (group chat, screenshot, ticket, clipboard history, `/tmp` logs of install output) can run arbitrary prompts on that machine forever; removePeer/setPeerState only drops roster records and never rotates the SK, so revocation is impossible without regenerating identity.json.
- mediumPeer SKs persisted in teams.json with default file mode while identity.json uses 0600
src/teams.js:24cmdAdd stores each peer together with its `sk` (master.js: addPeerToTeam(..., { ..., sk: peer.sk })), and teams.js/roster.js/memberships.js write those files with default permissions (typically 0644 in a 0755 directory), unlike identity.js which explicitly sets mode 0o600. Any other local user or process on a shared/CI host can read the roster and obtain credentials that grant remote task execution on every listed peer.
- lowInstaller opens port 47900 to all sources while the listener binds every interface
installer/install.sh:63The ufw rule is not restricted to a LAN subnet, and startListener uses server.listen(port) without a host argument, so on the advertised cloud-ECS topology the SK-authenticated task endpoint becomes internet-reachable. Protection then rests entirely on the single shared secret, with no rate limiting or TLS.
- lowRemote-supplied workspace path is used for mkdir and agent cwd without validation
src/task-runner.js:44A master can set task.workspace to any absolute path; the worker then creates directories there (mkdir recursive) and starts a session with cwd at that location plus fs/bash tools. Any authorized master can therefore drop task workspaces into sensitive directories (e.g. another project or a startup path) instead of the intended ~/.dsh/fleet/tasks area.
- lowMaster machineId is taken from the auth message without proof, so any card holder can impersonate another master
src/listener.js:44After the SK challenge-response, the listener trusts the self-asserted machineId/name and sends that master's control messages (including `kicked`) through onKicked. Because every master sharing a worker uses the same SK, any card holder can connect claiming another master's machineId and trigger deletion of that master's membership record, or forge hello/teams entries; the worker cannot distinguish masters.
Unencrypted TCP task channel with a taskId-only HMAC lets an in-path attacker run arbitrary agent prompts on workers; permanent SK in copyable cards and 0644 peer secrets add risk.
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-22 · activity: Stable
• Repo created: 2026-08-20
• Stars: ★ 4 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/scriptsnet/dsh-fleet
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 dsh-fleet?
dsh-fleet 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 dsh-fleet?
Run dsh plugin --profile web add dsh-fleet in a DeepSeek Harness (dsh) environment. That exact command passed a real install inside an isolated sandbox (L4) plus web smoke testing (L5).
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-19 (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.
