← All tools

majiayu000/dsh-plugin-registry

Popularity 50 Updated Development & Build

Searchable DeepSeek Harness plugin registry with curated listings and manifest-verified GitHub discovery.

githubauto-collected

Installation

A directly usable install command is not verified yet. Check the project documentation or releases.

Harness Registry — DeepSeek Harness Plugin Registry

Harness Registry is a searchable DeepSeek Harness plugin registry for DSH users and plugin authors. It combines a community-curated catalog with GitHub discovery, verifies the installable dsh.bundle manifest contract, and exposes comparable plugin metadata and copy-ready install commands.

Status: pre-release. The registry is available at plugin.dshdesk.com and the source is released under the MIT License. See launch readiness.

Quickstart

Requirements: Node.js 22 and npm.

git clone https://github.com/majiayu000/dsh-plugin-registry.git
cd dsh-plugin-registry
npm ci
npm run dev

Open <http://localhost:5173 to browse, search, filter, and inspect the registry.

What it provides

  • A searchable web directory with categories, trust labels, Stars, Forks, and install commands.
  • Curated entries vendored from the community catalog into sources/curated.json.
  • Automatic discovery from the GitHub dsh-plugin topic.
  • Manifest verification: discovered repositories must declare a valid dsh.bundle object in package.json, and its referenced patch file must exist.
  • Supply-chain pinning: each verified plugin records the exact verifiedCommit HEAD its manifest was checked against.
  • A public JSON snapshot with schema validation, health gates, and a separate audit queue.
  • Snapshot freshness on every page, with a stale warning past 24 hours and an automatic GitHub issue when a scheduled sync fails.
  • Strict per-page Content-Security-Policy with icons restricted to GitHub-hosted domains.
  • A repository checker that explains whether a plugin is eligible for automatic discovery.
  • An optional on-site review form that creates an assigned, public GitHub Issue through a protected Cloudflare Pages Function.

Query the registry data

The generated snapshot lives at public/data/plugins.json and follows schema/registry.schema.json.

jq '.stats | {published, curated, automaticallyDiscovered, pendingReview}' public/data/plugins.json

Inspect one plugin:

jq '.plugins[] | select(.id == "omdsh-dev/dsh-at-file") | {id, trustLevel, install}' public/data/plugins.json

Validate the snapshot and run the governance tests:

npm run validate:registry
npm test

Backfill GitHub primary-language metadata without rerunning full discovery: