Upgrade check
DeepSeek Harness 0.2.2 plugin compatibility
Every night our sandbox takes plugins that install on npm latest and installs them again, into a clean profile, on the upcoming next and alpha releases of DeepSeek Harness. It measures one thing — whether the plugin still installs and registers on that release — and not whether it behaves the same once it runs.
Plugin names, npm names or github:owner/repo, one per line or separated by spaces. Or paste your profile's package.json and its dependencies are read.
What the sandbox found
- next — DeepSeek Harness 0.2.2-rc.1: 147 of 148 plugins that install on latest still install. Last run 2026-11-05. 1 refused by the version check, 0 failed or timed out, 0 need a build approved first.
- alpha — DeepSeek Harness 0.2.2-alpha.3: 295 of 296 plugins that install on latest still install. Last run 2026-11-05. 1 refused by the version check, 0 failed or timed out, 0 need a build approved first.
Install on latest, not on the next release
Most-starred first. Only each plugin's newest run on the tag's current release counts.
| Plugin | Stars | next · 0.2.2-rc.1 | alpha · 0.2.2-alpha.3 |
|---|---|---|---|
| anweat/dsh-web-search-pro | 76 | refused | refused |
If one of yours breaks
Refused means the plugin's declared dsh range does not cover that release, and only its author can widen engines.dsh. Until then, staying on the DeepSeek Harness you run now is the fix.
Why DeepSeek Harness refuses plugins, and every way around it ›
The same data as JSON, CORS open, up to 100 names a call:
GET https://dshmarketplace.dev/api/v1/compat?names=dsh-better-sidebar,owner/repo