This repository has been renamed: XSakura666/dsh-plugin-ChronoAgent — click to visit the new location. Everything below is preserved as originally indexed.
Install verification: Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — the L1-L5 install ladder does not rate it; the security scan still runs. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.Install verification details →
Data as of (UTC)
What it doesAI
Local-first desktop app that schedules AI agent tasks like cron jobs, running automatically with files and web.
- Schedule AI tasks as cron jobs
- Local-first, zero token cost until run
- Integrates files, web, MCP tools, multi-model
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:XSakura666/ChronoAgent#dsh-pluginInstall method: GitHub · runtime test inconclusive (L5 unknown) · verified on dsh 0.2.0-rc.2
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.
3 samples (roughly every 5 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-18 → 10-05 · 3 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
Only 2 points (< 3): no chart yet
09-23 → 10-05 · 2 points
Reconstructed backwards from the current total using daily downloads (gaps are not interpolated)
Only 0 points (< 3): no chart yet
no data yet
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
Only 0 points (< 3): no chart yet
no data yet
Verification & Compatibility○ Ecosystem plugin
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.2 | dsh 0.2.0-rc.1 | dsh 0.1.7-rc.2 | dsh 0.1.7-rc.1 | dsh 0.1.7-alpha.2 |
|---|---|---|---|---|---|
| dsh-plugin | ○ | ○ | ○ | · | ○ |
| 5f27a4 | · | · | · | · | · |
| 47f5d5 | · | · | · | ○ | · |
dsh-plugingithub○ 11 ecosystem plugin2026-10-09
https://github.com/XSakura666/ChronoAgent
○dsh 0.2.0-rc.22026-10-09Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.2
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent#dsh-plugin
ID: chronoagent@dsh-plugin@dsh0.2.0-rc.2 · profile: l4-sandbox
Issued: 2026-10-09 · expires: 2026-10-16
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.2.0-rc.12026-09-29Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.2.0-rc.1
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent#dsh-plugin
ID: chronoagent@dsh-plugin@dsh0.2.0-rc.1 · profile: l4-sandbox
Issued: 2026-09-29 · expires: 2026-10-06
View checks & evidence
not present in web-profile loader inventory
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-26Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.2
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent#dsh-plugin
ID: chronoagent@dsh-plugin@dsh0.1.7-rc.2 · profile: l4-sandbox
Issued: 2026-09-26 · expires: 2026-10-03
View checks & evidence
not present in web-profile loader inventory
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-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent#dsh-plugin
ID: chronoagent@dsh-plugin@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
View checks & evidence
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.6-alpha.22026-09-20Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent#dsh-plugin
ID: chronoagent@dsh-plugin@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
View checks & evidence
not present in web-profile loader inventory
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-16Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent#dsh-plugin
ID: chronoagent@dsh-plugin@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-16 · expires: 2026-09-23
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○dsh 0.1.5-rc.22026-09-11Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent#dsh-plugin
ID: chronoagent@dsh-plugin@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
View checks & evidence
not present in web-profile loader inventory
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-08Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent#dsh-plugin
ID: chronoagent@dsh-plugin@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-08 · expires: 2026-09-15
View checks & evidence
not present in web-profile loader inventory
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 plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent#dsh-plugin
ID: chronoagent@dsh-plugin@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-07 · expires: 2026-09-14
View checks & evidence
not present in web-profile loader inventory
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 plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent#dsh-plugin
ID: chronoagent@dsh-plugin@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-12
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
○prehistory2026-10-04Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: unknown
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent#dsh-plugin
ID: chronoagent@dsh-plugin@dshunknown · profile: l4-sandbox
Issued: 2026-10-04 · expires: 2026-10-11
View checks & evidence
not present in web-profile loader inventory
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
5f27a4github2026-08-24
https://github.com/XSakura666/ChronoAgent
Ecosystem plugin: installs via dsh plugin add but declares no dsh.bundle and mounts no plugin capability — its level reads L4 · Ecosystem plugin (the not-bundle verdict comes from the install step; L5 does not apply). The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
47f5d5github○ 4 ecosystem plugin2026-09-24
https://github.com/XSakura666/ChronoAgent
○dsh 0.1.7-rc.12026-09-24Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent (version unstated)
ID: chronoagent@47f5d5@dsh0.1.7-rc.1 · profile: l4-sandbox
Issued: 2026-09-24 · expires: 2026-10-01
View checks & evidence
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-06Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/XSakura666/ChronoAgent (version unstated)
ID: chronoagent@47f5d5@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
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-alpha.12026-09-02Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: artifact unstated (historical)
ID: chronoagent@47f5d5@dsh0.1.2-alpha.1 · profile: l5-web-smoke
Issued: 2026-09-02 · expires: 2026-12-01
View checks & evidence
ecosystem plugin: no dsh.bundle declaration
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-23Ecosystem plugin
- • Node.js: v24.14.0
- • DSH: 0.1.1-rc.2
- • Plugin artifact: artifact unstated (historical)
ID: chronoagent@47f5d5@dsh0.1.1-rc.2 · profile: l4-sandbox
Issued: 2026-08-23 · expires: 2026-08-30
View checks & evidence
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:
`[](https://www.dsh.so/artifact/chronoagent/?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.
Static low; dynamic medium (authoritative when present) → overall medium.
v0.3.0dsh-plugingit2026-10-08dsh-pluginsame versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (7)
- criticalshellExec · shell
src/tools.js:93exec(cmd, { - warningfsWrite · files
genicon.js:94fs.writeFileSync(path.join(dir, 'icon.png'), png); - warningfsWrite · files
genicon.js:95fs.writeFileSync(path.join(dir, 'icon.ico'), ico); - warningchildProcess · code-exec
src/mcp.js:72this.proc = spawn(cfg.command, cfg.args || [], { - warningfsWrite · files
src/store.js:31fs.writeFileSync(tmp, JSON.stringify(this.data, null, 2), 'utf8'); - warningfsWrite · files
src/store.js:35fs.writeFileSync(this.filePath, JSON.stringify(this.data, null, 2), 'utf8'); - warningfsWrite · files
src/tools.js:53fs.writeFileSync(p, String(args.content != null ? args.content : ''), 'utf8');
show 5 audit findings
- mediumrun_command executes an LLM-supplied string via child_process.exec when the opt-in allowShell flag is on
src/tools.js:93With settings.allowShell enabled (unchecked by default, but a one-click GUI toggle), the model can run any shell command, and scheduled tasks execute automatically with no per-run confirmation. If a task's context was influenced by fetched web content, that content can escalate to arbitrary local code execution.
- mediumread_file/write_file are not confined to the workspace; absolute paths and ../ are accepted
src/tools.js:11An auto-running agent can read any file readable by the user (SSH keys, browser data, config) and overwrite any writable file — e.g. the app's own userData/data.json, which is re-parsed on next start and could turn on allowShell, or shell start-up files for persistence. The workspaceDir argument gives a false impression of sandboxing.
- lowhttp_request can reach any host including localhost and follows redirects automatically
src/tools.js:125The tool imposes no host restriction and uses fetch's default redirect handling, so model-influenced input can probe loopback/private addresses or internal metadata endpoints and POST to arbitrary services. This is largely the documented purpose of the tool, so it is a hardening gap rather than a bypass.
- lowAPI keys fall back to plaintext on disk when safeStorage encryption is unavailable
main.js:84Despite the comment claiming the plaintext key never hits disk, encryptSecret returns the raw key when safeStorage.isEncryptionAvailable() is false (or throws), so data.json stores the model API key in clear text.
- lowStored task text is later re-injected as an authoritative user message with no review
dsh-chrono-agent/index.js:207Task text created earlier (possibly derived from untrusted web content the agent fetched) is replayed as a fresh user instruction and executed with the agent's full tool set at a later time, giving a delayed injection channel that outlives the turn in which the untrusted data was seen. This is inherent to the plugin's design rather than a coding defect.
DSH entry dsh-chrono-agent/index.js is clean; risk sits in the bundled Electron agent's opt-in shell exec, unconfined file I/O and SSRF-capable HTTP tools.
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-16 · activity: Inactive
• Repo created: 2026-08-15
• Stars: ★ 1 · Forks: 0
• Health: Inactive — no commit in 90+ days
Source
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 ChronoAgent?
ChronoAgent is an ecosystem plugin listed on dsh.so: it installs with dsh plugin add but declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use its source repository directly. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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 ChronoAgent?
Run dsh plugin --profile web add github:XSakura666/ChronoAgent#dsh-plugin in a DeepSeek Harness (dsh) environment. Note this is an ecosystem plugin: it declares no dsh.bundle and mounts no plugin capability, so installing it adds no plugin functionality — use the source repository directly. The security scan still runs. The Web / Desktop plugin manager accepts only packages that declare dsh.bundle and refuses this one with not-bundle (rolling the install back); only `dsh plugin add` installs it, as a plain dependency.
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-17 (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.
