Know which DeepSeek Harness plugins break after every release—before users do.
English · 简体中文
Upstream Radar continuously retests a maintained fleet of exact published plugins against changing DeepSeek Harness (DSH) releases in disposable runners. When a pair breaks, it produces a reproducible issue; when the author ships a fix, it retests and closes the loop.
100 maintained install/load targets · 100 catalog entries across all 21 categories · 4 upstream reports closed
Latest full fleet run: 96 executable catalog cells observed · 67 compatible · 29 need review · 0 reproduced incompatibilities · 4 source-only. Review signals are never advertised as plugin failures.
A healthy repository does not prove that its published plugin still works. The artifact users install must resolve against a specific DSH host, Node runtime, profile, and dependency set—and any of them can change overnight.
Upstream Radar checks the relationship, not just the two repositories. A local pre-publish check asks, “does this plugin pass today?” Radar asks, “which maintained plugins stopped passing after the ecosystem changed?”
flowchart TB
Schedule["Scheduled GitHub Action"] --> Watch["Watch DSH + plugin releases"]
Watch --> Matrix["Exact plugin × DSH matrix"]
Matrix --> Static["Static contract checks"]
Matrix --> Runtime["Disposable runner: install → register → load"]
Static --> Evidence["Reproducible compatibility evidence"]
Runtime --> Evidence
Evidence --> Issue["One fixable issue"]
Issue --> Fix["Author publishes a fix"]
Fix --> Watch
Radar establishes the result with deterministic evidence. An optional DSH Agent can explain impact and suggest the next action, but a model never turns missing evidence into a pass.
- An exact result for
plugin version × DSH version × Node/profile, not a timeless “compatible” badge. - Static dependency and peer-contract checks joined with real install/register/load evidence from the published artifact.
- A maintained result that is retested when DSH or the plugin changes.
- One managed issue that is updated on repeat failures, reopened on regression, and closed after a clean retest.
We opened the following reports; their upstream maintainers have now closed them:
- Sanqi-normal/dsh-webui-market-plugin#5
- 1na-ko/dsh-hdc-bridge#3
- 6Mikao9/dsh-wsl-workspace#6
- 3274375092/dsh-voice#2
npx --yes upstream-radar@0.42.0 review dsh-plugin \
<package>@<version> \
--dsh-version <dsh-version>For code-executing checks, use the maintained isolated observer workflow: each pair receives a fresh, secret-free GitHub-hosted VM and restricted container.
Inspect the live compatibility matrix, the directory-consumable evidence feed, the first 50-plugin corpus, or the architecture notes.
If Upstream Radar helps the DSH ecosystem stay compatible, please give it a Star ⭐