Cross-session TODO board for DeepSeek Harness (dsh): a draggable floating panel groups tasks by working directory, each task carries a run mode (remind / auto-continue in the current session / auto-open a new session) and two checkboxes (AI done, user verified).
Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Draggable floating TODO board for dsh that groups tasks by directory with run modes and AI/user verification checkboxes.
- Draggable floating panel that works across sessions
- Groups tasks by working directory
- Run modes: remind/auto-continue/new session; tracks AI & user verification
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-todo-boardInstall 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
Based on 1 requirement(s) across 1 @deepseek-ai/dsh-* packages. raw ranges
>=0.1.7-rc.2 ×1
✓ Running dsh 0.2.1-rc.2 is within the declared range — install is not blocked by version.
Footnote: the author also wrote engines.dsh = ">=0.1.7-rc.2" — DSH does not read that field (not part of the verdict).
Whether it actually runs is a separate question → see the measured matrix below (L1–L5).
| 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.13.5 | · | · | · | · | · |
| 0.13.4 | ✓ | · | · | · | · |
| 0.13.1 | · | ✓ | ✓ | · | · |
| 0.12.0 | · | · | · | ✓ | · |
| 0.11.4 | · | · | · | · | ✓ |
0.13.5npm2026-10-24
dsh-todo-board
No runtime install test for this version (static scan only) — compatibility unknown, never assumed.
0.13.4npm✓ 1 runtime-verified2026-10-19
dsh-todo-board
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · dsh-todo-board@0.13.4
ID: dsh-todo-board@0.13.4@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.
0.13.1npm✓ 2 runtime-verified2026-10-16
dsh-todo-board
✓dsh 0.2.1-alpha.42026-10-16L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.4
- • Plugin artifact: npm · dsh-todo-board@0.13.1
ID: dsh-todo-board@0.13.1@dsh0.2.1-alpha.4 · profile: l4-sandbox
Issued: 2026-10-16 · expires: 2026-10-23
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-13L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-alpha.2
- • Plugin artifact: npm · dsh-todo-board@0.13.1
ID: dsh-todo-board@0.13.1@dsh0.2.1-alpha.2 · profile: l3-fullscan
Issued: 2026-10-13 · expires: 2026-10-20
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.12.0npm✓ 2 runtime-verified2026-10-10
dsh-todo-board
✓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-todo-board@0.12.0
ID: dsh-todo-board@0.12.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.
✓prehistory2026-10-04L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-todo-board@0.12.0
ID: dsh-todo-board@0.12.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.11.4npm✓ 2 runtime-verified2026-10-01
dsh-todo-board
✓dsh 0.2.0-rc.12026-09-30L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: npm · dsh-todo-board@0.11.4
ID: dsh-todo-board@0.11.4@dsh0.2.0-rc.1 · profile: l4-sandbox
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.
✓prehistory2026-10-01L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: npm · dsh-todo-board@0.11.4
ID: dsh-todo-board@0.11.4@dshunknown · profile: l4-sandbox
Issued: 2026-10-01 · expires: 2026-10-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.
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/dsh-todo-board/)``[](https://www.dsh.so/artifact/dsh-todo-board/)``[](https://www.dsh.so/artifact/dsh-todo-board/)``[](https://www.dsh.so/artifact/dsh-todo-board/)``[](https://www.dsh.so/artifact/dsh-todo-board/)``[](https://www.dsh.so/artifact/dsh-todo-board/)``[](https://www.dsh.so/artifact/dsh-todo-board/)`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 high; dynamic medium (authoritative when present) → overall medium.
v0.13.5dsh manifest0.13.5npm2026-10-240.13.5same versionsuspicious · npmVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningnetIp · network
tools/capture-screenshots.mjs:28const APP = process.env.DSHTB_URL ?? 'http://127.0.0.1:3080' - warningnetIp · network
tools/capture-screenshots.mjs:44const res = await fetch(`http://127.0.0.1:${PORT}${path}`) - warningnewFunction · code-exec
tools/check-fence-parity.mjs:61const harnessIsTrusted = new Function( - warningnewFunction · code-exec
tools/check-fence-parity.mjs:72const oursRejection = new Function( - warningnetIp · network
tools/check-fence-parity.mjs:101{ host: '127.0.0.1:3080', origin: 'http://127.0.0.1:3080' }, - warningnetIp · network
tools/check-fence-parity.mjs:103{ host: '127.0.0.1:3080', origin: 'https://127.0.0.1:3080' }, - warningnetIp · network
tools/check-http.mjs:65const base = 'http://127.0.0.1:' + port - warningnewFunction · code-exec
tools/check-template-parity.mjs:37return new Function('return ' + literal + ".join('\\n')")()
show 2 audit findings
- mediumFallback board route trusts any loopback Host and omits browser-session auth
tools/check-http.mjsIn a deployment without the harness connection service, any local process (including an AI with a shell) can POST /dsh-todo-board/api with a loopback Host and no browser session, creating, dispatching or editing todos and bypassing the model-tool approval gate.
- lowScreenshot tool writes page URL/HTML/text to assets on failure
tools/capture-screenshots.mjsIf DSHTB_URL contains a DSH session token, or the page contains real todo/note content, the failure path persists it to assets/capture-debug.json; assets is included in npm files, so the artifact can be committed or published.
Runtime files are absent; the supplied tests show the board route fallback accepts unauthenticated local writes when the harness connection gate is missing.
Rule (2026-10-24): when a dynamic conclusion exists it is authoritative (it may raise or lower the level); without one, the static/vet fused tier applies. 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 static/vet.
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-10-23 · activity: Active
• Repo created: 2026-09-09
• Stars: ★ 3 · Forks: 1
• Health: Active — committed within last 30 days
Source
GitHub: github.com/sueqet/dsh-todo-board
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).