The original repository has been deleted or made private. This page is an archival snapshot from indexing time; the install command may no longer work.

dsh-my-todo avatar

dsh-my-todo

Global cross-session todo list plugin for DeepSeek Harness: my_todo tool, /todo command, and an openable conversation view tab

Ecosystem appProductivityAutomationStorageMemoryStorage
Verification
L5 · Ecosystem app
Risk
Out of scope
Health
Inactive
Trust
Silver

Install verification: Ecosystem app: not installed via dsh plugin add, so the L1-L5 plugin install-verification ladder does not apply; the security scan still runs.Install verification details →

Data as of (UTC)

What it doesAI

Global cross-session todo list plugin with tool, command, and conversation tab for DeepSeek Harness.

  • Provides my_todo tool for managing todos
  • Includes /todo command for quick access
  • Opens a conversation view tab for todo list
productivityAImemoryAIstorageAI

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

GitHub repository

Ecosystem apps are not installable via dsh plugin add: desktop / web shells install or deploy through their own release channel (GitHub Releases or the project site).

The level reads L4 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (ecosystem plugins are decided by the install step not-bundle check, so L5 does not apply; the ladder does not rate them); the security scan still runs.

Verification & Compatibility◼ Ecosystem app

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

Install compatibility matrix (rows = plugin versions〔latest 5〕, columns = dsh versions〔latest 5〕)
◼ Ecosystem app
At-a-glance → evidence in the cards below
plugin \ dshdsh 0.1.5-rc.2dsh 0.1.3-alpha.2dsh 0.1.3-alpha.1dsh 0.1.2-rc.1dsh 0.1.2-alpha.1
e45b3e·····
9b3667◼◼◼✗✗
Install compatibility (by plugin version, dsh versions within)
Legend:✓ L5 runtime verified○ ecosystem plugin◼ ecosystem app✗ failed
e45b3egithub2026-08-24

https://github.com/wangweber/dsh-my-todo

Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.

9b3667github◼ 4 ecosystem app2 failed2026-09-11

https://github.com/wangweber/dsh-my-todo

◼dsh 0.1.5-rc.22026-09-11Ecosystem app
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.5-rc.2
  • • Plugin artifact: github · https://github.com/wangweber/dsh-my-todo (version unstated)
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Unknown
L5 runtime
Not tested
Ecosystem app: not installed via `dsh plugin add` (desktop / web shell) and no install verdict was produced — it ships through its own release channel and the L1-L5 ladder does not rate it (shown as L5 · ecosystem app)
Ecosystem app

ID: dsh-my-todo@9b3667@dsh0.1.5-rc.2 · profile: l4-sandbox

Issued: 2026-09-11 · expires: 2026-09-18

View checks & evidence
L1 · Found✓ Passed
L2 · Structured✓ Passed
L3 · Install spec✓ Passed
L4 · Install tested? Unknown
Sandbox install verdict? Unknown
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-11
spec github:wangweber/dsh-my-todo · channel GitHub source · outcome unknown
L5 · Run tested– Not tested

This level was not executed in this scan.

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-09Ecosystem app
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.3-alpha.2
  • • Plugin artifact: github · https://github.com/wangweber/dsh-my-todo (version unstated)
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Unknown
L5 runtime
Not tested
Ecosystem app: not installed via `dsh plugin add` (desktop / web shell) and no install verdict was produced — it ships through its own release channel and the L1-L5 ladder does not rate it (shown as L5 · ecosystem app)
Ecosystem app

ID: dsh-my-todo@9b3667@dsh0.1.3-alpha.2 · profile: l4-sandbox

Issued: 2026-09-09 · expires: 2026-09-16

View checks & evidence
L1 · Found✓ Passed
L2 · Structured✓ Passed
L3 · Install spec✓ Passed
L4 · Install tested? Unknown
Sandbox install verdict? Unknown
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-09
spec github:wangweber/dsh-my-todo · channel GitHub source · outcome unknown
L5 · Run tested– Not tested

This level was not executed in this scan.

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 app
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.3-alpha.1
  • • Plugin artifact: github · https://github.com/wangweber/dsh-my-todo (version unstated)
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Unknown
L5 runtime
Not tested
Ecosystem app: not installed via `dsh plugin add` (desktop / web shell) and no install verdict was produced — it ships through its own release channel and the L1-L5 ladder does not rate it (shown as L5 · ecosystem app)
Ecosystem app

ID: dsh-my-todo@9b3667@dsh0.1.3-alpha.1 · profile: l3-fullscan

Issued: 2026-09-07 · expires: 2026-09-14

View checks & evidence
L1 · Found✓ Passed
L2 · Structured✓ Passed
L3 · Install spec✓ Passed
L4 · Install tested? Unknown
Sandbox install verdict? Unknown
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-06
spec github:wangweber/dsh-my-todo · channel GitHub source · outcome unknown
L5 · Run tested– Not tested

This level was not executed in this scan.

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 app · L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.2-rc.1
  • • Plugin artifact: github · https://github.com/wangweber/dsh-my-todo#9b3667
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Failed
Sandbox install failed
Ecosystem app · L5 · failed

ID: dsh-my-todo@9b3667@dsh0.1.2-rc.1 · profile: l3-fullscan

Issued: 2026-09-05 · expires: 2026-09-12

View checks & evidence
L1 · Found✓ Passed
L2 · Structured✓ Passed
L3 · Install spec✓ Passed
L4 · Install tested✓ Passed
Install succeeded✓ Passed
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-09-04
spec github:wangweber/dsh-my-todo · install mode reused L4 scratch
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

✗dsh 0.1.2-alpha.12026-09-06Ecosystem app · L5 · failed
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.2-alpha.1
  • • Plugin artifact: github · https://github.com/wangweber/dsh-my-todo (version unstated)
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Failed
Sandbox install failed
Ecosystem app · L5 · failed

ID: dsh-my-todo@9b3667@dsh0.1.2-alpha.1 · profile: l3-fullscan

Issued: 2026-09-06 · expires: 2026-09-13

View checks & evidence
L1 · Found✓ Passed
L2 · Structured✓ Passed
L3 · Install spec✓ Passed
L4 · Install tested✓ Passed
Install succeeded✓ Passed
L5 · Run tested✕ Failed
Sandbox install passed✓ Passed
check took: 0ms
Web boot ready✕ Failed
plugin tree failed to load
HTTP endpoint served✕ Failed

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

◼dsh 0.1.1-rc.22026-08-28Ecosystem app
Environment & artifact
  • • Node.js: v24.14.0
  • • DSH: 0.1.1-rc.2
  • • Plugin artifact: github · https://github.com/wangweber/dsh-my-todo#9b3667
Levels (L1–L3 plugin-level static archive · L4/L5 newest real verdicts for this combination)
L1 static
Passed
L2 static
Passed
L3 static
Passed
L4 sandbox
Passed
L5 runtime
Not tested
Install test ran: the package installs, but this is an ecosystem app (desktop / web shell) — not installed via `dsh plugin add`; it ships through its own release channel and the L1-L5 ladder does not rate it (shown as L5 · ecosystem app)
Ecosystem app

ID: dsh-my-todo@9b3667@dsh0.1.1-rc.2 · profile: l3-fullscan

Issued: 2026-08-28 · expires: 2026-09-04

View checks & evidence
L1 · Found✓ Passed
L2 · Structured✓ Passed
L3 · Install spec✓ Passed
L4 · Install tested✓ Passed
Install executed in confined sandbox✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-08-23
spec github:wangweber/dsh-my-todo · channel GitHub source · outcome ran · exit 0
check took: 3.8s
Install succeeded✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-08-23
spec github:wangweber/dsh-my-todo · channel GitHub source · outcome ran · exit 0
check took: 3.8s
Installed artifact confirmed✓ Passed
Source: Windows ACL sandbox · Method: sandbox install run · Captured 2026-08-23
spec github:wangweber/dsh-my-todo · channel GitHub source · outcome ran · exit 0
check took: 3.8s
L5 · Run tested– Not tested

This level was not executed in this scan.

L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.

Author badges

Embed the dsh.so badges in your README to show this plugin's automated security-scan and install-test status:

dsh.so risk badge
`[![dsh.so risk](https://cdn.dsh.so/badge/dsh-my-todo.svg)](https://www.dsh.so/artifact/dsh-my-todo/?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.

dsh-my-todoAutomated review · daily

Static high; dynamic low (authoritative when present) → overall low.

static high→dynamic low→overall low
dynamic findings0 critical·0 high·0 medium·1 low
lowoverall · low
1static scan · vet primaryvet AST static analysis (npm artifact or git source)
plugin versionv0.1.0dsh manifest
scanned version0.1.0git2026-09-12
current versione45b3e60cdecversion moved on
vet verdictsuspicious · git

Vet is an AST static scan (npm artifact or git source).

2model reads redacted source context · never executes plugin code
highest gradelow
merged intooverall low
audited at2026-10-24
audited artifactgit 7730d7c51154fa04317629853a015950ccf1d219
findings0 critical·0 high0 medium / 1 low hidden
show 1 audit findings
  • lowBrowser API accepts arbitrary todo status string, which silently drops that item on the next loadsrc/routes.ts:86

    The `update` branch casts any caller-supplied string to TodoStatus without checking it, unlike the tool/command paths. store.update assigns it and persist() writes it, but isValidTodo() on next startup only accepts pending/in_progress/completed, so the item is filtered out and lost from the persisted list. Reachable only from the fenced loopback route, so the actor is the local user/page, not a remote attacker.

Global todo plugin: file-backed store, model tool, /todo command, and a loopback-fenced POST /todo/api route; no exploitable issue, one minor unvalidated-status gap.

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-20 · activity: Inactive

• Repo created: 2026-08-19

• Stars: ★ 0 · Forks: 0

• Health: Inactive — no commit in 90+ days

Source

GitHub: github.com/wangweber/dsh-my-todo

Frequently asked questions

What is dsh-my-todo?

dsh-my-todo is an ecosystem app listed on dsh.so, not a DSH plugin package: it cannot be installed with dsh plugin add and ships through the project's own release channel.

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-my-todo?

This is an ecosystem app, not a plugin installable via dsh plugin add: desktop / web shells install or deploy through their own release channel. The security scan still runs, but the L1-L5 plugin install ladder does not rate it.

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-10-24 (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.

Was this page helpful?