dsh-update-checker

Managing a DSH workstation means npm packages and GitHub-sourced plugins scattered across the profile, lockfile, and node_modules. Checking for updates typically requires manually querying the registry, comparing commits, and parsing pnpm output that mixes success messages with real errors on the same stream. dsh-update-checker consolidates all of this into a single filterable table under Settings > Update Check, showing updatable, up-to-date, prerelease, and failed items at a glance.

Detection is tailored to each source. For npm packages it compares against latest, next, and the highest published version. For GitHub packages it reads the remote HEAD and all release tags via git ls-remote (no API rate limit) and falls back to the GitHub API automatically, so detection still succeeds when github.com:443 is blocked. A single ls-remote call also reveals tags, so a dependency pinned to a release reads as "installed v0.1.24, target v0.1.26", rather than appearing perpetually outdated because the branch moved. When an update fails, the plugin strips pnpm noise and classifies the real cause - blocked git channel, a build script refused by the supply-chain policy, a release-age hold, or a network issue - quoting the exact configuration line needed.

It suits developers who maintain a DSH environment with both npm and GitHub plugins, particularly under restricted networks or profiles that require human approval for third-party build scripts. Both checking and updating run as background tasks that never block a request; if a package must execute its own build script, the panel first displays the target file, the exact allowlist line, and the side effects, writing nothing until you confirm.