awesome-dsh-plugin Ships a dsh Market Index (Oct 18, 2026)

awesome-dsh-plugin Becomes a dsh 0.2.1 Plugin Market Index, Served from npm.

The same 2026-10-18 window that delivered 166 additions and the list’s largest repository-gone delisting also carried a structural change: the awesome-dsh-plugin list stopped being only an awesome list. A commit landing 2026-10-18 09:29:12 UTC — “feat: publish the list as a DSH plugin market index” — states the context in its own opening lines: “dsh 0.2.1 added plugin market indexes: one JSON document (format 1) a host reads as a market source, browsed in the official Plugins → Discover tab and by the plugin_market agent tool. This list becomes one.”

What a host actually does

The README’s new opening note (present in the 2026-10-19 fetch) gives the concrete instruction: on dsh 0.2.1+, open Plugins → Discover → Index sources and add https://cdn.jsdelivr.net/npm/dsh-plugin-catalog/index.json. From then on, per the same note, the Discover tab and the plugin_market agent tool search the same entries the README lists. The connection to this site’s release coverage is the release line itself: v0.2.1-alpha.4 shipped “plugins can be discovered and installed from custom plugin index sources” in its New Features section, and the list’s launch commit names dsh 0.2.1 as the version that added plugin market indexes — the same series, seen this time from the list’s side of the interface.

npm-only, and why the bytes come from npm

The index’s coverage boundary is stated twice, at two levels of precision. The README: “The index covers plugins published on npm with a known version; GitHub-only entries still install with the command beside them.” The launch commit explains what format 1 is missing: “GitHub-only entries (about half the list) cannot be expressed yet — format 1 wants a commit SHA per Git version, and this repository records none.” The measured numbers agree with the estimate: this site’s 2026-10-19 fetch read 2,953 entries in the index against 5,932 in the list’s data/plugins tree.

The delivery channel is a timeout story. Per the README: “dsh gives a source 15 seconds, and the GitHub Pages copies of the same document — https://awesome-dsh-plugin.com/index.json and its mirror https://dshmarket.com/index.json — can exceed that from some networks.” Hence the npm-served jsDelivr copy is the address to add. All three URLs answered HTTP 200 in the 2026-10-19 fetch; the jsDelivr and dshmarket.com copies were byte-identical (2,320,845 bytes) while awesome-dsh-plugin.com served a slightly smaller document (2,319,351 bytes).

Three fixes in one afternoon

The launch did not survive the day unchanged. A 13:02 UTC commit added “a CDN copy, and minify, for the host’s 15 s fetch budget”; 13:09 UTC trimmed “what a card cannot show, and make the npm copy the address to add”; and 13:56 UTC moved the index to “ride in the catalog package; a new npm package needs a browser step” — withdrawing the standalone publish script added an hour earlier. The final state ships index.json inside the existing dsh-plugin-catalog npm package, whose registry entry reads latest version 2026.1018.7728, published 2026-10-18 14:24 UTC.

One build-time guarantee is quoted in the commit itself: the index “is built from the same data as the site and validated with @deepseek-ai/dsh-plugin-market-index — the parser every host runs — so the bytes that leave here cannot be a document DSH rejects”. That parser package’s own registry entry reads latest version 0.2.1-alpha.4, published 2026-10-15 — versioned with the same alpha this site covered when the index-source feature first appeared in release notes.

What a host actually does

npm-only, and why the bytes come from npm

Three fixes in one afternoon

More in this series