我们拆了 1.1 万个 DeepSeek Harness 插件，发现官方几乎没有建立插件治理机制

TL;DR - An audit of roughly 11,000 repositories tagged as DeepSeek Harness plugins finds a largely ungoverned ecosystem with weak discovery, compatibility, and trust mechanisms. The most serious issue is that plugins run with the user’s full account privileges, unaffected by Harness’s advertised file-permission modes.

• Plugin counts are misleading: 93% of 1,883 reviewed repositories reportedly could not be installed under Harness conventions, often because they lacked required manifests, dependencies, or layouts.
• DeepSeek provides no official plugin directory, compatibility matrix, signing, verification, security-reporting channel, or recommendation list; GitHub tagging has no admission controls.
• A probe plugin could read SSH filenames and environment secrets, write files, and access the network even in read-only mode because permission controls govern model tool requests, not plugin code.
• Popular plugins can conflict over shared UI or configuration paths, while adding tools can invalidate prompt-prefix caches, increase context usage, and make tool selection less reliable.