Preface¶

The philosophy of DSH is “everything is a plugin.” In practice, however, developers still need to verify item-by-item questions such as where plugins can be discovered, whether they can be installed, and what information can be seen before installation.

NanmiCoder/dsh-plugin-market provides a Web UI plugin marketplace entry point for DeepSeek Harness: browse the catalog first, then check installation evidence and trust levels, and finally confirm the installation or removal of a plugin. Below is an introduction to its positioning, installation method, and typical usage.

What This Is¶

NanmiCoder/dsh-plugin-market is a DSH plugin maintained by NanmiCoder, licensed under MIT.

It connects the DSH plugin catalog to a Web UI, allowing developers to discover, inspect, install, and remove plugins directly from the interface:

• Discover DSH plugins;
• Check installation evidence and trust levels for each entry;
• Install or remove verified plugins from the Web UI.

Core Features¶

It primarily provides the following capabilities:

1. Adds a plugin marketplace to DeepSeek Harness.
2. Browse a continuously curated catalog under Settings → Plugin Marketplace.
3. Check installation evidence and trust levels for each entry.
4. Install or remove verified plugins from the Web UI.
5. Search by repository name, package name, topic, category, and controlled tags.
6. Display repository descriptions, model summaries, topics, metrics, licenses, release data, and installation evidence.
7. The host validates normalized npm/Git specifications before installation, then invokes pnpm.
8. Supports previewing the commands to be executed before confirming installation.
9. Supports installation, removal, and dynamic profile coordination.
10. Supports allowInstall: false browsing mode.

Installation and Activation¶

A DeepSeek Harness installation is required before proceeding.

npm Installation¶

First, execute the installation command:

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

This step adds the plugin to the web profile.

Next, verify the combined profile:

dsh --profile web --dump-config

This step is used to confirm the merge result of the current profile.

Then restart DSH and open the Web UI:

dsh web

Once completed, open:

Settings → Plugin Marketplace

Source Installation¶

To install from source, first clone the repository:

git clone https://github.com/NanmiCoder/dsh-plugin-market.git

Enter the repository directory, then install dependencies and build:

pnpm install
pnpm build

Then install the local directory into the web profile:

dsh plugin --profile web add .

Local plugin installation will link to this source code. After modifying the source code, rebuild by running:

pnpm build

Typical Usage¶

Browsing the Catalog¶

After opening Settings → Plugin Marketplace, you can search entries by repository name, package name, topic, category, and controlled tags.

Each entry displays:

• Repository description;
• Model summary;
• Topics;
• Metrics;
• License;
• Release data;
• Installation evidence.

Checking Installation Evidence¶

Before installation, review the installation evidence and trust levels for the corresponding entry.

When confirming installation, the interface displays the commands that will be executed. The confirmation dialog shows the repository, author, license, package source, and build script risks.

The key point of this step is: look at the evidence first, then decide whether to proceed with installation.

Installation and Removal¶

You can install or remove verified plugins from the Web UI.

The host is responsible for validating normalized npm/Git specifications, then invoking pnpm, and handling installation, removal, and dynamic profile coordination.

Browse Mode¶

If you only want to browse without performing installations or removals, you can configure:

allowInstall: false

allowInstall: false will reject all installation/removal changes, retaining only browsing capabilities.

Use Cases and Considerations¶

Suitable for developers who need to centrally discover DSH plugins in the Web UI and review evidence and commands before installation.

Things to keep in mind:

• Installing third-party plugins executes third-party code on your local machine.
• Plugins run with the privileges of the current dsh process; check the source code and license before installation.
• Deterministic verification proves packaging and installability, not that third-party plugins are harmless.
• The npm package contains only a small seed catalog, not a multi-MB live dataset; registryUrl must be configured when deploying a standalone directory.
• The host routes use /plugin-hub/*, not /plugins/<package-id>.
• The UI registers under settings.section for compatibility with DSH builds that do not expose settings.plugins.tab.

Conclusion¶

The value of NanmiCoder/dsh-plugin-market lies in bringing the discovery, inspection, and installation actions of DSH plugins into a single Web UI flow, allowing you to see entry evidence, execution commands, and trust levels before installation.

Repository:

https://github.com/NanmiCoder/dsh-plugin-market

Catalog page:

https://www.skillhub.cn/plugins/NanmiCoder/dsh-plugin-market