
cyber-moshen/dsh-plugin-market
31Last commit Aug 15, 2026
dsh-plugin-market DSH plugin
Plugin Workshop adds a dedicated page to DSH Settings where you can discover community plugins in a card grid with live GitHub stats, search, and filter by tags or maintenance status. It supports one-click install/update/uninstall via the `dsh plugin` CLI, includes a safety net that prevents broken plugins from leaving the profile unbootable, and provides a settings modal for GitHub token and auto-update preferences.
How to install the dsh-plugin-market DSH plugin
dsh plugin --profile web add @cyber-moshen/dsh-plugin-marketCopying does not run this command. Review the repository and version before installing the dsh-plugin-market DSH plugin.
dsh-plugin-market DSH plugin data source
dsh-plugin-market DSH plugin snapshot date: Aug 16, 2026
discovered
What the dsh-plugin-market DSH plugin can do
- Search and filter plugins by name, author, tags, install state, stars, commit date, and maintenance status.
- One-click install, update, and uninstall plugins directly from the web UI.
- Safety net: pre-install dependency audit, post-install boot-composition check with automatic rollback.
- GitHub integration: shows live star count, last commit time, and maintenance color indicator for each plugin.
- Settings modal: configure GitHub token to raise API rate limit, toggle auto-update on startup.
- Hot reload for pure-JS plugins: no restart needed after installing/updating (native modules prompt for restart).
Where the dsh-plugin-market DSH plugin fits
- Discover new plugins for DSH web GUI and install them with one click.
- Keep installed plugins up to date with automatic update checks and manual update buttons.
- Manage installed plugins: uninstall, view version status, and see GitHub stats.
- Submit your own plugin to the community catalog by opening a pull request to the data/plugins.json file.
- Repair a broken DSH profile using the offline repair script included in the plugin.
Who the dsh-plugin-market DSH plugin is for
- DSH web GUI users who want to extend the interface with community plugins.
- Plugin developers who want to publish and distribute their plugins through a central catalog.
dsh-plugin-market DSH plugin limitations
- Requires a running DSH web GUI (profile web) — cannot be used in CLI-only mode.
- Depends on GitHub API for live stats; without a token, rate limit is 60 requests/hour, which may throttle the workshop.
- Installation and updates rely on npm package registry; offline or disconnected environments may not work.
- The safety net only covers plugins installed via the workshop; plugins installed directly via CLI may bypass the checks.
- Auto-update on startup only works for the web server, not for all DSH profiles.
dsh-plugin-market DSH plugin: from the repository README
Quoted from the cyber-moshen/dsh-plugin-market README, the upstream source of the dsh-plugin-market DSH plugin. Copyright remains with the original authors.
**Plugin Workshop** for the [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) web GUI — a curated plugin catalog that lives in this very repo. [中文](README.zh.md) · [日本語](README.ja.md) ## What it is A **Settings → Plugin Workshop (插件工坊)** page with: - a **card grid** of community plugins — each card shows **tags** (click a tag to search it), **GitHub stars**, **last-commit freshness** with a colored maintenance signal, and the **installed version / update state**; - **search across names, authors and tags**, plus an always-visible filter bar (installed state, sort by stars/commit, maintenance state); - **one-click install / update** (runs the real `dsh plugin` CLI in the background); - a **GitHub icon button** on every card jumping straight to the repo; - a **settings modal** with a **GitHub Token** field (lifts API rate limits) and a **startup auto-update** toggle; - the **whole workshop follows the app's own language** (Settings → General → Language: 中文 / English); - a frame-wide toast after a boot-time auto-update — pure-JS plugins hot-reload in place, plugins with native modules ask for a restart. - **hot reload** — installing/updating/uninstalling a pure-J
Read the full READMERepository license: MIT
dsh-plugin-market DSH plugin questions
How do I install the Plugin Market plugin itself?
Run `dsh plugin --profile web add @cyber-moshen/dsh-plugin-market` from the command line. Then restart the web server. After that, you'll find a new 'Plugin Workshop' page under Settings. The plugin itself can be updated via the workshop once it's installed.
How can I add my own plugin to the marketplace?
Open a pull request against the `data/plugins.json` file in the dsh-plugin-market repository. Add an entry with your plugin's GitHub URL, npm package name, and optional tags. A validation workflow will check the JSON format. The card name, author, and stats are derived from the URL automatically.
Why do I see a warning about 'fan-out' when installing a plugin?
The safety net detects that the plugin's dependency tree contains multiple packages that declare `dsh.bundle`, which could cause duplicate loader entries. This is common with 'kitchen-sink' aggregate plugins. The warning requires you to explicitly confirm you understand the risk before proceeding. The post-install boot-composition check then validates the final bundle stack and rolls back if it fails.
How do I use a GitHub token with the Plugin Workshop?
Open the Settings modal in the workshop (next to the search box). Paste a classic personal access token with the `repo` scope into the GitHub Token field and click Save. The token is stored in the profile's configuration. You can also set it via environment variables `GITHUB_TOKEN` or `GH_TOKEN`, which take precedence. A token raises the API rate limit from 60 to 5000 requests per hour.
What happens if I install a plugin that breaks the web interface?
The workshop's safety net prevents this. Before installation, it audits dependencies for bundle fan-out. After installation, it runs a boot-composition check in a throwaway subprocess. If the check fails, the plugin is automatically uninstalled and the profile's `package.json` is restored from a snapshot. In case your profile is already broken (e.g., from a CLI install), use the offline repair script: `node <plugin-checkout>/scripts/repair.mjs --profile web`.