dsh-plugin-market

English · 简体中文

Find the real plugins. Install the safe ones.

dsh-plugin-market adds a plugin marketplace to DeepSeek Harness. Browse a continuously curated catalog inside Settings → Plugin Marketplace, inspect the evidence behind each entry, and install or remove verified plugins without leaving the Web UI.

The catalog is deliberately conservative: deterministic rules decide whether an artifact is installable; model-generated summaries and tags are display-only and never authorize an install.

Open the interactive WebUI preview to search the real catalog slice, inspect evidence, and test the responsive product flow without executing an installation.

Current catalog proof

The repository snapshot generated on 2026-08-15 contains:

Every one-click action executes a normalized package spec from the catalog—not a shell command copied from a repository README.

Why Plugin Market?

Install

[!NOTE] Requires an existing DeepSeek Harness installation.

npm

dsh plugin --profile web add @nanmicoder/dsh-plugin-market

Validate the composed profile, restart DSH, and open the Web UI:

dsh --profile web --dump-config
dsh web

Then open Settings → Plugin Marketplace.

Build from source

git clone https://github.com/NanmiCoder/dsh-plugin-market.git
cd dsh-plugin-market
pnpm install
pnpm build
dsh plugin --profile web add .

Run pnpm build again after changing the source. The local plugin install remains linked to this checkout.

How it works

1. The crawler discovers repositories from the dsh-plugin, deepseek-harness, and dsh GitHub topics.
2. GitHub metadata, root and workspace manifests, patch files, README content, releases, and npm registry manifests are collected.
3. Deterministic rules assign one of four trust tiers and derive the only spec that may be executed.
4. The model adds a concise summary, category, tags, and the author's stated install hint. These fields never change the tier or executable spec.
5. Versioned catalog artifacts are published under data/v1/; the plugin refreshes them with ETag requests and keeps a local cache.
6. The Web UI merges catalog entries with the active profile's installed state. An install sends only an entry ID back to the host.
7. The host looks up that ID in its own catalog, validates the normalized spec, runs pnpm add, reconciles dsh.profile.bundles, and hot-mounts the plugin row.

Trust model

README hints are evidence, not commands

Each entry keeps two values separate:

This prevents hard-coded profile names, template placeholders, shell metacharacters, and stale package names in README prose from entering the execution path.

Marketplace experience

• Filter one-click entries, the full catalog, or already installed plugins.
• Search across repository names, package names, topics, categories, and controlled tags.
• Open a detail panel for full repository metrics, install evidence, and the source README.
• See exactly which command the marketplace will execute before confirming.
• Install, uninstall, and reconcile the active profile without editing its manifest by hand.
• Switch the plugin to browse-only mode with allowInstall: false.

README files are fetched on demand through a catalog-ID route. The renderer builds React elements rather than using dangerouslySetInnerHTML, and links and images are limited to safe HTTP(S) URLs.

Configuration

- insert:
    - id: plugin-hub
      name: '@nanmicoder/dsh-plugin-market'
      config:
        registryUrl: ''
        refreshIntervalHours: 6
        allowInstall: true

Boundaries

• Installing a third-party plugin executes third-party code on your machine. The confirmation dialog exposes repository, author, license, package source, and build-script risk before any change.
• Deterministic verification proves packaging and installability, not that a third-party plugin is benign. Review unfamiliar code before installing it.
• The npm package includes a small seed catalog, not the multi-megabyte live dataset. Configure registryUrl when deploying against a separately published catalog.
• Host routes use /plugin-hub/*. They intentionally stay outside /plugins/<package-id>, which DSH reserves for client bundles.
• The UI registers into settings.section for compatibility with DSH builds that do not expose settings.plugins.tab.

Catalog development

cp .env.example .env          # add ANTHROPIC_API_KEY for model labels
pnpm crawl:dry                # full crawl into .tmp/, without changing data/
pnpm crawl:rules              # deterministic classification only
pnpm crawl                    # crawl, classify, and label
pnpm refresh                  # refresh and push only when content changes

Install hints are extracted with the Anthropic SDK. The default DeepSeek-compatible endpoint and model can be overridden with LLM_BASE_URL and LLM_MODEL; classification remains rule-based regardless of the model provider.

Development

pnpm install
pnpm typecheck
pnpm build
pnpm verify
pnpm site:dev
pnpm site:build
npm pack --dry-run --ignore-scripts

pnpm verify runs offline catalog, install-safety, request-trust, crawler, labeling, artifact, and package-contract checks.

Every pushed commit is type-checked, built, and deployed through Vercel's Git integration. main updates production; other branches receive preview deployments.

Releasing

Normal commits and pushes never publish npm packages. A release tag must exactly match package.json:

pnpm version patch --no-git-tag-version
git add package.json pnpm-lock.yaml
git commit -m "chore: release v$(node -p \"require('./package.json').version\")"
git push origin main
git tag "v$(node -p \"require('./package.json').version\")"
git push origin --tags

The publish.yml workflow rebuilds from source, verifies the package and tarball, then publishes through npm Trusted Publishing (OIDC). No long-lived NPM_TOKEN is required.

License

MIT