Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it does
DSH 待办清单:左侧导航、Agent 工具与可置顶的独立窗口。
Installation
dsh plugin --profile web add github:AsakuraAOI/dsh-todoInstall method: GitHub · 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
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.1-rc.2 current |
|---|---|
| 0d0e00 | ✓ |
0d0e00github✓ 1 runtime-verified2026-10-19
https://github.com/AsakuraAOI/dsh-todo
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: github · https://github.com/AsakuraAOI/dsh-todo (version unstated)
ID: dsh-todo@0d0e00@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.
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-todo/)``[](https://www.dsh.so/artifact/dsh-todo/)`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 low — stricter wins → overall low.
v0.3.0dsh manifest0.3.0git2026-10-210.3.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (6)
- warningfsWrite · files
native/main.cjs:64}).catch(error => { if (smokeReport) fs.writeFileSync(smokeReport, JSON.stringify({ error: error.stack })); app.exit(1); }); - warningfsWrite · files
native/smoke.cjs:33await win.webContents.capturePage().then(image => fs.writeFileSync(path.join(path.dirname(report), 'details.png'), image.toPNG())); - warningfsWrite · files
native/smoke.cjs:51await win.webContents.capturePage().then(image => fs.writeFileSync(path.join(path.dirname(report), 'compact.png'), image.toPNG())); - warningfsWrite · files
native/smoke.cjs:111await win.webContents.capturePage().then(image => fs.writeFileSync(path.join(path.dirname(report), 'panel-details.png'), image.toPNG())); - warningchildProcess · code-exec
src/window.js:77const child = spawn(executable, [], { env, windowsHide: true, stdio: ['ignore', 'ignore', 'pipe'] }); - warningnetIp · network
src/window.js:74const env = { ...process.env, DSH_TODO_ENDPOINT: `http://127.0.0.1:${server.address().port}/rpc`, DSH_TODO_TOKEN: token, DSH_TODO_DATA_ROOT:
show 1 audit findings
- lowEnv-inherited smoke harness can run webContents.executeJavaScript and write arbitrary-path files
native/main.cjs:63src/window.js spawns the child with {...process.env, DSH_TODO_*}, so a DSH_TODO_SMOKE_REPORT already present in the DSH host environment activates native/smoke.cjs even when the parent never set options.smokeReport. That path calls win.webContents.executeJavaScript, captures PNGs and writes JSON to the path given in the variable (also in the catch branch of app.whenReady). It requires control over the host process environment, i.e. strong local access already, so real impact is limited; the harness only fails/aborts (fixture-theme RPC answers 400) because the server-side smoke gate stays off.
Electron todo companion is well hardened: loopback token-authed RPC, origin/JSON checks, sandboxed renderer, validated inputs; only an env-gated test harness remains low risk.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
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-18 · activity: Active
• Repo created: 2026-10-18
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
GitHub: github.com/AsakuraAOI/dsh-todo
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
