All plugin categories
DSH Plugin Category

DeepSeek Harness Security & Policy Plugins

Discover DSH plugins for permission controls, security auditing, policy enforcement, plugin vetting, credentials, recovery, and safer agent operation.

1057 indexed pluginsSorted by popularityPage 5 of 30View newestRecently updated
View plugin tarocub

tarocub

cloveric/tarocub

15GitHub stars
Indexed

Feishu/Lark-first local AI agent gateway and native DeepSeek Harness plugin for Codex, Claude Code, Kimi Code, DeepSeek Harness, and Antigravity; Telegram optional.

DSH Profile: webv0.1.350MIT
View plugin
View plugin DSH_VsCodeMode

DSH_VsCodeMode

Lenonss/DSH_VsCodeMode

12GitHub stars
Manifest Valid

VSCode-style coding for DeepSeek Harness: Monaco editor (tabs/QuickOpen), agent edit-diff review (keep/reject/archive/rollback), LSP intelligence with VSIX installs

DSH Profile: webv0.5.3MIT
View plugin
View plugin dsh-agent-plugins-market

dsh-agent-plugins-market

Sivan757/dsh-agent-plugins-market

12GitHub stars
Manifest Valid

A DeepSeek Harness plugin that adds a web-based marketplace for installing and runtime-injecting agent plugin suites from Git repositories.

DSH Profile: <name>vdsh-agent-plugins-market-v0.7.1MIT
View plugin

About DeepSeek Harness Security & Policy Plugins

Security and policy plugins inspect, restrict, audit, or recover parts of a DeepSeek Harness environment. This category covers permission rules, plugin vetting, configuration audits, credential controls, access gates, rollback and recovery mechanisms, policy enforcement, and security-focused diagnostics. Protection and enforcement levels differ by implementation, so the Registry keeps source and verification evidence visible instead of reducing plugins to a generic safe label.

When evaluating a security plugin, first determine whether it reports findings or actively blocks and modifies behavior. Review its enforcement point, required privileges, documented fail-open or fail-closed behavior, files and credentials it accesses, dependencies, lifecycle scripts, repository activity, and compatibility evidence. A Security Signal describes observable evidence; it is not itself a security certification.