Are DeepSeek Harness plugins safe?

Most community DSH plugins are safe and well-intentioned, but they run with your dsh process's permissions and GitHub-sourced plugins may execute build scripts at install time. Verify the source, license, and activity before installing.

Can a DSH plugin run code on my machine?

Yes. Plugins run as part of your agent loop with the same permissions as your dsh process, and installation from GitHub may trigger build scripts. This is why you should only install plugins you trust.

How do I install a DSH plugin safely?

Install only from trusted sources, read the source code, check the license, pin a commit hash (dsh plugin add github:owner/repo#sha), keep plugins updated, and use a dedicated profile for untrusted plugins.

What should I check before installing a DSH plugin?

Check the repository (README, code, issues), the license (prefer MIT/Apache-2.0), recent activity, and the maintainer's reputation. Curated directories pre-filter for these signals.

Are DSH Plugins Safe? Remote Code, Permissions, and Best Practices

Security questions come up constantly in the DeepSeek Harness community, and for good reason: a DSH plugin runs with your agent’s permissions. This guide explains the real risks and gives you a practical checklist.

How plugins actually run

A DeepSeek Harness plugin is code that runs inside your agent loop:

At install time, plugins fetched from GitHub may execute build scripts. The harness asks for approval, but the code runs on your machine.
At runtime, a plugin can read files, call tools, make network requests — anything your dsh process can do.

That’s the model. It’s powerful and it’s the same model used by most agent tools. Safety comes from verification, not from sandboxing you can’t see.

The three real risks

Install-time code execution — a plugin’s build script runs on your machine when you install it.
Runtime permissions — a malicious or compromised plugin can exfiltrate data or modify files within your process’s reach.
Supply-chain compromise — a popular plugin can be taken over (account hijack, malicious release, abandoned repo republished).

A practical safety checklist

Install only from sources you trust — prefer known maintainers and repos with history.
Read the source — at least skim the README and the install/build script. You don’t need to understand everything; you need to see what it will run.
Check the license — permissive licenses (MIT, Apache-2.0) with an explicit LICENSE file are a good sign. A repo with no license is a yellow flag.
Check activity — recent pushes and resolved issues indicate maintenance. An abandoned plugin is a security risk, not just a quality risk.
Pin the commit — dsh plugin add github:owner/repo#sha gives you reproducible, reviewable installs.
Keep plugins updated — security fixes arrive in new releases; but test before upgrading.
Isolate — if your harness supports profiles, run untrusted plugins in a dedicated profile.

What curated directories do (and don’t) do

This directory reviews plugins before listing them: purpose, documentation, license, and activity. Every listing links directly to its GitHub source so you can do your own review.

What we can’t do is guarantee safety — no directory can. The final decision is always yours, and the checklist above is the tool for it.

If something goes wrong

Remove the plugin: dsh plugin remove <name>
Check what changed: inspect recent files and outbound connections if you suspect compromise.
Report it: flag the repository and alert the community (GitHub issues on the plugin repo and on ecosystem lists).

The bottom line

DSH plugins are generally safe, and the community is overwhelmingly well-intentioned. The risk profile is manageable with basic verification. Read the installation guide for the mechanics, then use the checklist above before every install.