🗑️ 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: 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
Runs validated deterministic Python rule programs before DeepSeek Harness model calls, self-evolving them from approved request history.
- Executes verified deterministic rules before LLM calls; routing itself uses no model
- Self-evolves rule files via DSH tool loop, verifier feedback and immutable releases
- Scoped to read-only verifiable tasks like listing files; falls back to the DSH agent
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.
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.2 | dsh 0.1.7-rc.1 | dsh 0.1.7-alpha.1 | dsh 0.1.6-alpha.2 | dsh 0.1.6-alpha.1 |
|---|---|---|---|---|---|
| v0.1.0-alpha.1 | · | · | · | · | ✗ |
v0.1.0-alpha.1github1 failed2026-09-30
https://github.com/Riderich/self-evolving-router-dsh
✗dsh 0.1.6-alpha.12026-09-17Ecosystem app · L5 · failed
- • Node.js: v24.14.0
- • DSH: 0.1.6-alpha.1
- • Plugin artifact: github · github:Riderich/self-evolving-router-dsh#v0.1.0-alpha.1#v0.1.0-alpha.1
ID: self-evolving-router-dsh@v0.1.0-alpha.1@dsh0.1.6-alpha.1 · profile: l5-web-smoke
Issued: 2026-09-17 · expires: 2026-12-16
View checks & evidence
↳ carried from earlier record self-evolving-router-dsh@v0.1.0-alpha.1@dshunknown (l3-fullscan)
↳ carried from earlier record self-evolving-router-dsh@v0.1.0-alpha.1@dshunknown (l3-fullscan)
↳ carried from earlier record self-evolving-router-dsh@v0.1.0-alpha.1@dshunknown (l3-fullscan)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
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/self-evolving-router-dsh/?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 no conclusion (static stands) → overall low.
v0.1.0-alpha.1dsh manifestv0.1.0-alpha.1git2026-10-07v0.1.0-alpha.1same versionclean · gitVet is an AST static scan (npm artifact or git source).
not in the dynamic queue (the queue only covers plugins whose static tier is medium or above — medium/high/critical; since 2026-10-24 entries rated low are not audited even when dsh-only rules logged warnings) — this does not mean the dynamic audit found it safe.
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-14 · activity: Stable
• Repo created: 2026-09-14
• Stars: ★ 0 · 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 self-evolving-router-dsh?
self-evolving-router-dsh 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 self-evolving-router-dsh?
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-07 (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.