w2112515/dsh-plugin-marketplace
30Last commit Aug 15, 2026
dsh-plugin-marketplace DSH plugin
DSH Plugin Marketplace is an out-of-tree, installable DSH bundle that adds a full plugin marketplace to DeepSeek Harness. It provides a static catalog of 2,200+ plugins discovered by daily GitHub scans, with evidence-based install eligibility, consent-gated scripts, and zero telemetry. The UI is bilingual and follows DSH's display language automatically.
How to install the dsh-plugin-marketplace DSH plugin
dsh plugin --profile web add @w2112515/dsh-plugin-marketplaceCopying does not run this command. Review the repository and version before installing the dsh-plugin-marketplace DSH plugin.
dsh-plugin-marketplace DSH plugin data source
dsh-plugin-marketplace DSH plugin snapshot date: Aug 16, 2026
discovered
What the dsh-plugin-marketplace DSH plugin can do
- Browse 2,200+ plugins across nine categories with search and freshness meters
- Evidence-based install eligibility: automatic installs only if every target file exists at the pinned commit
- Consent-gated script execution: lifecycle scripts are shown verbatim and run only after explicit per-install consent
- Community ratings via GitHub reactions on a dedicated issue, with no verdict below 10 votes
- Agent-native: four tools (search, detail, install, manual guide) callable by the DSH agent with one-time human approval
- Solution packs: curated lists of plugins that install multiple items in one reviewed action
- Static catalog served from GitHub Pages, no server, no telemetry, no install counts
Where the dsh-plugin-marketplace DSH plugin fits
- Discover new DSH plugins from a community-maintained catalog without leaving the Settings UI
- Install plugins with safety guarantees: automatic installs skip all lifecycle scripts, script-gated installs require explicit review
- Use solution packs to install a coherent set of plugins (e.g., top-rated per category) in one action
- Evaluate plugin popularity via community ratings (GitHub 👍/👎) with recency windows
- Let DSH agents search and install plugins on your behalf after human approval
Who the dsh-plugin-marketplace DSH plugin is for
- DSH users who want to extend their harness with additional plugins
- Plugin authors who want their plugins to be discoverable in the marketplace
- Power users who prefer agent-assisted plugin management
dsh-plugin-marketplace DSH plugin limitations
- Requires DSH installed with the web profile; only works in the Settings UI within DSH
- Automatic installs require the host to have pnpm 11 (corepack pnpm also tried); script-gated installs need pnpm ≥ 11.7
- The catalog is read-only against a static JSON file; no server-side updates or user accounts
- Script-gated installs cannot be automated; they require manual review and consent in the WebUI
- Manual install entries (no build output, no lifecycle scripts) only provide a repository link; the marketplace never runs anything
- Solution packs grant no privilege: script-gated items still need per-plugin review and consent
dsh-plugin-marketplace DSH plugin: from the repository README
Quoted from the w2112515/dsh-plugin-marketplace README, the upstream source of the dsh-plugin-marketplace DSH plugin. Copyright remains with the original authors.
**The plugin marketplace for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (DSH): browse, review, and install DSH plugins from inside DSH's own Settings UI — with evidence-based install safety, consent-gated install scripts, curated solution packs, and zero telemetry.** **中文文档：[README.zh-CN.md](README.zh-CN.md)**（界面语言跟随 DSH 自动切换） ## What is DSH Plugin Marketplace? DSH Plugin Marketplace is an **out-of-tree, installable DSH bundle** that adds a full plugin marketplace to DeepSeek Harness. It is not part of the official DSH repository, requires no changes to DSH source code, and is not a standalone web product. Once installed into the `web` profile, DSH's Host Loader mounts the marketplace Host plugin, and the package's declared `dsh.client` browser entry registers itself under `Settings → Plugins → Marketplace`. The UI is bilingual and follows DSH's display language automatically (中文 / English). At a glance: - **2,200+ plugins** discovered by a daily scan of every GitHub repository carrying the `dsh-plugin` topic — no GitHub account or token needed to browse. - **Evidence-based install eligibility**: the scanner proves which install targets exist at each p
Read the full READMERepository license: MIT
dsh-plugin-marketplace DSH plugin questions
How do I install the DSH Plugin Marketplace into my DSH?
Run the following command in your terminal: `dsh plugin --profile web add @w2112515/dsh-plugin-marketplace`. You can also pin to an immutable commit: `dsh plugin --profile web add github:w2112515/dsh-plugin-marketplace#<40-char-commit>`. After installation, restart `dsh web` to activate the marketplace in Settings → Plugins → Marketplace.
Do I need a GitHub token to use the marketplace?
No. The marketplace uses a static catalog served from GitHub Pages, which is generated by a daily GitHub Actions scan. The browser never talks to the GitHub API directly, and regular users need no GitHub account or token to browse or install plugins.
How do I uninstall the marketplace?
Run `dsh plugin --profile web remove @w2112515/dsh-plugin-marketplace`. This will remove the bundle and its associated configuration. You can verify the removal by checking that the Marketplace tab no longer appears in DSH Settings.
Can I submit my own plugin to the marketplace?
Yes. To be discoverable, your repository must have the `dsh-plugin` topic, a `package.json` declaring `dsh.bundle.patch`, and a valid `cordis.patch.yml`. You can optionally add a `dsh-category-<slug>` topic to set the catalog category. The marketplace's daily scanner will automatically pick up your repository if it meets these criteria.
What happens if an install script is involved?
Script-gated installs are shown verbatim in the review step. After you explicitly consent, the Host installs once with `--allow-build=<name>` instead of `--ignore-scripts`, scoping execution to exactly that package. Consent is never persisted; each install requires separate approval. Manual entries (no build output, no scripts) only show a repository link.