How to find DeepSeek Harness plugins on GitHub

Start from three different evidence layers

The official DeepSeek Harness repository defines the CLI, profile, and bundle behavior. The public dsh-plugin topic is a discovery surface that any repository owner can apply. A curated registry is narrower: it attempts to connect a project to a package or source target that can be reviewed for installation.

Those layers answer different questions. Official documentation explains how DSH works; the Topic reveals what people are publishing; a curated entry supplies a more specific install claim. Never treat a Topic count or star count as a package manifest check.

Five checks before choosing a repository

• Identity: the package, repository, author, and README should point to the same project.
• Install evidence: look for a declared DSH bundle or patch and a package or pinned Git target.
• Profile: confirm whether the plugin belongs in web, desktop, headless, or a custom profile.
• Freshness and maintenance: inspect recent source activity, releases, unresolved issues, and archived status.
• License and execution boundary: understand what code runs, which files or credentials it can reach, and whether build scripts are involved.

A practical discovery path

Search DSH Radar Discover when you want the broad GitHub topic. Narrow to curated matches when you need explicit install evidence. Open the repository and compare the current README with the directory snapshot. If a package name moved, a repository was archived, or the README now recommends a different target, prefer the current source and wait for the directory record to be corrected.

For exact plugin-name searches, use a dedicated review page when available. It preserves the public snapshot, explains source changes, and makes clear whether an install action is verified, stale, or intentionally withheld.