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.
Install verification: runtime verified (L5) · last checked Install verification details →
Data as of (UTC)
What it doesAI
Adds a calendar and per-day plan cards to the DSH Web GUI, with recurring plans and model-facing planning tools for the agent.
- Calendar view with per-day plan cards in the DSH Web GUI
- Supports recurring plans
- Model-facing tools let the agent read/write plans
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 github:qcsjjjjj/dsh-planner#v0.1.0Install 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.0-rc.1 | dsh 0.1.7-rc.2 | prehistory |
|---|---|---|---|
| v0.1.0 | ✓ | ✓ | ✓ |
v0.1.0github✓ 3 runtime-verified2026-10-05
https://github.com/qcsjjjjj/dsh-planner
✓dsh 0.2.0-rc.12026-09-29L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/qcsjjjjj/dsh-planner#v0.1.0
ID: dsh-planner@v0.1.0@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
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-27L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/qcsjjjjj/dsh-planner#v0.1.0
ID: dsh-planner@v0.1.0@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-27 · expires: 2026-10-04
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: github · https://github.com/qcsjjjjj/dsh-planner#v0.1.0
ID: dsh-planner@v0.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.
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-planner/?ref=badge)``[](https://www.dsh.so/artifact/dsh-planner/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-planner/?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 low (authoritative when present) → overall low.
v0.1.0dsh manifestv0.1.0git2026-10-07v0.1.0same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- criticalnewFunction · code-exec
.dev/render-calendar.mjs:11new Function('window', readFileSync(SRC, 'utf8'))(fakeWindow); - criticalnewFunction · code-exec
.dev/smoke-client.mjs:28new Function('window', readFileSync(SRC, 'utf8'))(fakeWindow); - warningfsWrite · files
.dev/smoke-host.mjs:296fs.writeFileSync(seriesFile, 'not json at all', 'utf8'); - warningfsWrite · files
.dev/smoke-host.mjs:300fs.writeFileSync(seriesFile, goodSeriesText, 'utf8'); - warningfsWrite · files
.dev/smoke-store.mjs:422fs.writeFileSync(store.fileFor(TODAY), '{ 这不是 JSON', 'utf8'); - warningfsWrite · files
.dev/smoke-store.mjs:434fs.writeFileSync(store.seriesFile, 'not json at all', 'utf8'); - warningfsWrite · files
.dev/smoke-store.mjs:443fs.writeFileSync(store.seriesFile, goodSeries, 'utf8'); - warningfsWrite · files
lib/store.js:190fs.writeFileSync(fd, text, 'utf8');
show 1 audit findings
- lowDev-only test harness executes the plugin source via new Function; not a shipping risk
.dev/render-calendar.mjs:11This construct (also present in .dev/smoke-client.mjs) compiles and runs the string read from ../client/client.js. It is a static, repo-local file whose path is derived via import.meta.url; no external or attacker-controlled input reaches it, and package.json "files" lists only lib, client, cordis.patch.yml and README.md, so the .dev/ directory is never installed or executed by the DSH runtime. Impact is limited to running the repo's own test suite, i.e. no reachable security effect; it is reported only to explain the static-scan critical heuristic.
Harvested code is a calendar/plan store with regex-validated dates before every path join, so no traversal; the only eval-like construct sits in a dev-only script excluded from published files.
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-09-25 · activity: Stable
• Repo created: 2026-09-25
• Stars: ★ 1 · Forks: 0
• Health: Stable — committed within 90 days
Source
GitHub: github.com/qcsjjjjj/dsh-planner
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 @qcsjjjjj/dsh-planner?
@qcsjjjjj/dsh-planner 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 @qcsjjjjj/dsh-planner?
Run dsh plugin --profile web add github:qcsjjjjj/dsh-planner#v0.1.0 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-10-16 (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.