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
Local-first Kanban/taskboard plugin for DeepSeek Harness with multiple views and per-task AI chat.
- Multi-view board: Kanban, list, Gantt, workflow, dashboard
- Per-task AI chat integrated into the board
- Local SQLite storage, no cloud dependency
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 @ttmouse/dsh-taskboardInstall 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-05 → 11-18 · 7 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
09-11 → 11-17 · 61 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
09-11 → 11-18 · 62 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.5.0 | ✓ | ✓ | ✓ | ✓ | ✓ |
0.5.0npm✓ 14 runtime-verified2026-11-17
@ttmouse/dsh-taskboard
✓dsh 0.2.2-rc.32026-11-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.3
- • Plugin artifact: npm · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.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-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.2-rc.1
- • Plugin artifact: npm · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.0@dsh0.2.2-rc.1 · profile: l4-sandbox
Issued: 2026-11-05 · expires: 2026-11-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.
✓dsh 0.2.1-rc.52026-11-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.5
- • Plugin artifact: npm · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.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 · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.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 · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.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 · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.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 · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.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 · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.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 · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.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 · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.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.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: npm · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.0@dsh0.1.7-alpha.2 · profile: l4-sandbox
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 · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.0@dsh0.1.6-alpha.2 · profile: l3-fullscan
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 · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.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.
✓prehistory2026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · @ttmouse/dsh-taskboard@0.5.0
ID: dsh-taskboard-4@0.5.0@dshunknown · profile: l3-fullscan
Issued: 2026-09-30 · expires: 2026-10-07
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-taskboard-4/?ref=badge)``[](https://www.dsh.so/artifact/dsh-taskboard-4/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-taskboard-4/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-taskboard-4/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-taskboard-4/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-taskboard-4/?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 medium (authoritative when present) → overall medium.
v0.5.0dsh manifest0.5.0npm2026-11-190.5.0same versionclean · npmVet is an AST static scan (npm artifact or git source).
show static findings (5)
- warningchildProcess · code-exec
lib/check-gate.mjs:44spawn('taskkill', ['/pid', String(child.pid), '/T', '/F'], { stdio: 'ignore' }) - warningchildProcess · code-exec
lib/check-gate.mjs:94const child = spawn(command.trim(), { - warningnetIp · network
lib/client.js:330var DSH_WEB_URL = "http://127.0.0.1:3080"; - warningnetIp · network
lib/index.mjs:120const target = new URL(req.url, 'http://127.0.0.1') - warningnetIp · network
lib/index.mjs:555baseUrl = `http://127.0.0.1:${address.port}`
show 4 audit findings
- mediumBoard-configured pre-check command is executed through the platform shell in the host process
lib/check-gate.mjs:94runInProcessClaim loads automation.checkCommand from GET /api/projects/:id/automation (a record writable through the board API proxied at /dsh-taskboard/*) and passes it to runCheck, which spawns it with shell:true and the full host environment. Anyone who can write that automation record obtains command execution in the host process with the user's privileges and env secrets. Reachable when automation is enabled and the project has a todo task.
- mediumConvention check script inside a project workspace is auto-executed without configuration
lib/check-gate.mjs:72When a workspace project has automation enabled and no explicit checkCommand, any file at scripts/schedule-checks/check.mjs in that workspace is executed by the host on every claim round as the host user, inheriting the full host env (API keys/tokens). A repository dropped into a synced workspace therefore supplies code that the host runs automatically.
- mediumEmbedded board iframe can queue arbitrary prompts into the host agent and create workspaces at any path
lib/client.js:407The bridge only type-checks the payload: payload.prompt is queued into the active GUI agent session (full tool access) and payload.workspacePath is registered as a DSH workspace at any filesystem path. Any script executing inside the embedded board page (e.g. XSS in board-rendered task content or AI output, whose rendering lives in the unaudited vendor/web tree) escalates to host agent execution and arbitrary-path workspace creation. The event.source === frame.contentWindow check does prevent external windows from spoofing.
- lowVendored server and agent-skill trees are loaded at runtime but absent from the audited source
lib/index.mjs:24createTaskboardServer handles all board HTTP/API/SQLite traffic (input validation for projects, tasks, automation, comments is entirely in the unsubmitted vendor/server tree), and syncAgentSkill copies vendor/skills/manage-taskboard into ~/.agents/skills, feeding agent instructions into every profile. Neither tree was included, so these runtime-critical surfaces could not be verified.
Medium risks: shell-executed board check commands, implicit execution of workspace check scripts, and an iframe-to-agent bridge lacking payload validation; vendored code unaudited.
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-04 · activity: Active
• Repo created: 2026-08-17
• Stars: ★ 5 · Forks: 3
• Health: Active — committed within last 30 days
Source
GitHub: github.com/ttmouse/dsh-taskboard
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-taskboard?
dsh-taskboard 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-taskboard?
Run dsh plugin --profile web add @ttmouse/dsh-taskboard 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.
