About DeepSeekPlugins.org

Directory scope

The catalog focuses on DSH plugins: repositories that extend DeepSeek Harness through its plugin architecture. This includes interface bundles, tools, memory layers, session controls, workflow engines, model routes, notifications, themes, development utilities, and experimental runtime components.

General products that call DeepSeek models are outside this catalog unless they also ship a DSH plugin. That boundary keeps the primary search task precise.

Sources and evidence

1. Official product facts. The DeepSeek Harness repository owns the product description, preview status, base CLI guidance, and official discovery links.
2. Community registry records. The awesome-dsh-plugin registry supplies names, owners, categories, descriptions, install commands, npm references, stars as recorded by that source, and addition dates.
3. GitHub repository snapshots. Selected records include stars, forks, language, license, topics, and source activity captured from the public GitHub API.
4. Local failure fallback. A curated snapshot keeps core discovery pages usable when the community endpoint times out or changes shape.

Current local snapshot date: 2026-08-14. The stored registry total is 249 records across 11 categories.

Normalization and failure handling

The live endpoint is fetched on the server and cached for 15 minutes. Records must provide a valid name, owner, known category, English description, and install command. Invalid rows are dropped. A structurally incomplete response triggers the local fallback.

The browser receives normalized JSON from this site. Remote descriptions are rendered as text. Install commands can be copied, and the directory never executes them. Favorites and theme preferences stay in local browser storage.

Limitations

A directory record can become stale between source refreshes. GitHub stars measure attention, and they do not establish quality or safety. A repository can change after it was reviewed. DeepSeek Harness can also change its plugin interfaces during developer preview.

Verify the repository, revision, license, permissions, dependency tree, install scripts, external services, secret handling, and current compatibility before using third-party code.

Corrections and catalog changes

Plugin metadata is maintained through the public community registry. For additions or corrections, follow that project's contribution workflow and include source evidence. Security concerns should also be reported privately to the affected plugin maintainer when public disclosure could create risk.

Open the community registry on GitHub