Version tracking with dsh.so Analysis — not just replication, but interpretation: what a release means for users, and what it means for plugins.
This is the release that matters for new users: the dsh family is now publicly installable from npm without special access. `npx @deepseek-ai/dsh web` serves the Web UI at http://127.0.0.1:3080. GitHub Releases still has no tagged artifacts — the source of truth for version history is the npm registry and the master branch. Expect the plugin surface (dsh.bundle / dsh.client manifests) to evolve.
| Plugin | Status | Note |
|---|---|---|
modlens | unknown | Declares dsh.bundle manifest; not yet verified by dsh.so. |
dsh-opencode-usage | unknown | Declares dsh.client manifest; not yet verified by dsh.so. |
dsh-launcher-windows | unknown | External Windows launcher; no dsh manifest. |
The 0.1.0 series began the same day as the ecosystem explosion: 300+ repositories with the dsh-plugin topic appeared shortly after. dsh.so treats 0.1.0-rc as the first stable-enough baseline for compatibility claims, but nothing has been independently verified yet.
| Plugin | Status | Note |
|---|---|---|
modlens | unknown | Author-declared bundle manifest; not yet tested by dsh.so. |
dsh-launcher-windows | unknown | External Windows launcher; no dsh manifest. |
The very first public npm artifact. DeepSeek Harness entered developer preview, and `npx @deepseek-ai/dsh web` became a working one-command install. No GitHub Release tag was published for this version — version history is tracked via npm and repository commits.
| Plugin | Status | Note |
|---|---|---|
modlens | unknown | Plugin ecosystem had not yet formed. |