DISCOVERY · EVIDENCE · REVIEW

Find reviewed DeepSeek Harness plugins

Search an evidence-led DSH plugin directory with pinned source commits, package structure, license details, compatibility signals, and transparent review notes.

Third-party plugins are untrusted code. Inclusion means the native bundle structure was observed at one fixed commit; it is not a safety or compatibility endorsement.

DEEPSEEK HARNESS PLUGIN DIRECTORY

What is a DeepSeek Harness plugin?

A DeepSeek Harness plugin is a bundle that extends the harness with tools, interfaces, skills, workflows, or external integrations. A native bundle connects a package manifest to a DSH patch at a specific source revision.

This directory helps developers discover DSH plugins without treating a topic tag or moving branch as proof. Every public record links back to immutable source evidence and keeps capability facts separate from trust decisions.

Evidence before recommendation

Each record keeps the source, structure, license, lifecycle, and capability facts visible instead of compressing them into a score.

01

Immutable source

Repository evidence is linked to a full commit SHA, never only to a moving branch.

02

Native structure

The package manifest and referenced DSH patch are checked at the same revision.

03

Independent facts

Licenses, lifecycle scripts, capability signals, and compatibility evidence stay separate.

COMMON QUESTIONS

DeepSeek Harness plugin FAQ

Short answers about discovery, review status, compatibility, safety, and catalog updates.

What is a DeepSeek Harness plugin?

It is a bundle that extends DeepSeek Harness with tools, interfaces, skills, workflows, or integrations. This index looks for the package manifest and DSH patch that define the bundle at one fixed commit.

How are DSH plugins discovered?

Automated discovery searches GitHub topics and structure-related queries. Matches enter a candidate queue only; they are not published until a fixed-source review is completed.

Does reviewed mean safe to install?

No. Reviewed means the repository structure and recorded evidence were inspected statically. The index does not execute third-party code, and static inspection cannot prove safe runtime behavior.

How do I check plugin compatibility?

Open the plugin record and compare its declared DSH versions, lifecycle scripts, package identity, patch, and pinned source against your own Harness version before installation.

How often is the plugin directory updated?

Candidate discovery runs on a schedule. Public catalog changes remain review-gated and appear after the reviewed data is merged into the main repository branch.