Security & Permissions

What it is — DeepSeek Harness penetration testing mode plugin for recording targets, exploring clues, and displaying web views.

Who it is for — Users conducting authorized penetration testing in DeepSeek Harness who need to record exploration chains and assets can install it. Users not requiring asset view display need not install.

Watch out — Sandbox testing passed: successfully registered in a fresh profile. Requires Node.js >= 22.5.

The verdict — Prerequisites single-session operation. I would install it because it provides dedicated storage backend for penetration records.

What it is — DeepSeek Harness plugin providing second-model auto-review on the approval chain.

Who it is for — When you use an agent in DeepSeek Harness to handle sandbox boundary actions, needing structured allow/deny review results. If your workflow relies more on human approval rather than subagent decisions, you don't need to install this plugin.

Watch out — Sandbox test passed, successfully installed in new profile and registered by harness. Requires providing API key or token upon installation. Will execute shell commands.

The verdict — I would install it because it implements a fail-closed default policy that prevents unsafe actions from passing when review fails.

What it is — Provides remote access gate for DeepSeek Harness with account/password auth, MFA (TOTP) login, browser-based directory picker, and account settings page.

Who it is for — It suits people who deploy DeepSeek Harness remotely and need in-browser directory selection for workspaces. It is not needed when you only use DSH in local loopback mode.

Watch out — The plugin must be restarted with dsh web for changes to take effect. Sandbox testing passed in a fresh profile and it registered successfully. API key or token is required.

The verdict — I would install it because it replaces the native OS directory picker with a double-column browser view and uses HMAC-SHA256 signed cookies for session security.

What it is — Integrates nine redteam security research modes and fifteen runtime plugins.

Who it is for — Suitable for installation when redteam security research needs mode support and tool plugins. Not needed if you are writing normal business code.

Watch out — Sandbox test passed: successfully registered in a fresh profile. It will execute shell commands. No other obvious issues found.

The verdict — I would install it for authorized redteam security research because it provides structured modes and tools, but only under the premise of authorized use.

What it is — This plugin delivers declarative permission rules for DeepSeek Harness, using ordered allow/deny/ask YAML to match tool names, arguments, workspace paths, and agent identity on the tools/pre-execute waterfall, with full audit, dry-run, and hot reload.

Who it is for — When you want to restrict agent tool calls in DeepSeek Harness based on specific rules for names, params, paths, and identity, this plugin is suitable. If your workflows do not require such matching rules or session logging, you do not need to install it, as another angle is that it is designed for complex permission scenarios involving multiple decision layers.

Watch out — Sandbox testing passed after installation in a fresh profile and registration with harness. Static checks indicate it can execute shell commands, but this is only a hint, not a defect. No obvious runtime issues were found.

The verdict — I would install it because the rules-first approach paired with AI reviewer backstop allows deterministic decisions before model involvement, providing a value in auditable tool execution control.

What it is — Adds a server-grade multi-tenant plugin to DeepSeek Harness for remote access and auto HTTPS.

Who it is for — When sharing DeepSeek Harness on a server for team use requiring subuser permissions and token/daily quotas. If your usage is purely local single-machine without multi-user access and permissions management, you can skip it.

Watch out — Installation requires no extra configuration. Sandbox testing passed in a new profile. No obvious issues found.

The verdict — I would install it because it enables subuser permissions and token/daily quotas for team sharing on servers, but only if not using it locally.

What it is — A local security audit plugin integrated with DeepSeek Harness, generating redacted risk reports.

Who it is for — When using the headless profile of DeepSeek Harness for auditing local configuration, plugin origins, and sessions, this plugin is suitable. Those primarily doing remote model operations without local file exposure checks do not need it.

Watch out — Sandbox test passed: installed into a new profile and successfully registered by harness. No obvious issues found.

The verdict — I will install it because it supports report actions for risk summarization in local environments.

What it is — DeepSeek Harness plugin enabling remote web launch with username/password authentication.

Who it is for — If you need to securely access the DeepSeek Harness web interface from your local network, this plugin enables username/password login. If you only use the command-line interface of DeepSeek Harness without needing the web UI, you do not need this plugin.

Watch out — Requires providing an API key or token. Sandbox testing passed: successfully installed in a fresh profile and registered with harness. No obvious issues found.

The verdict — I would install it because it allows secure remote access to the DeepSeek Harness web interface with authentication.

What it is — DeepSeek Harness plugin that inserts Auto permission preset, letting classifier auto-approve routine sandbox escalations once.

Who it is for — Suitable for developers handling long tasks and dependency installs who want to reduce manual interruptions with a classifier model. Not suitable for users who want to avoid any human approval, because dangerous operations still require manual review.

Watch out — Tested successfully: installed in fresh profile and registered with harness. Classification calls have timeout that falls back to manual. No obvious issues found.

The verdict — I would install it because it reduces interruptions for routine tasks, but only if you configure a classifier model to avoid timeouts.

What it is — DShScan is a DeepSeek Harness plugin security scanner. It can assess plugin risks and output scores and security suggestions.

Who it is for — When you are managing the dshbase plugin directory on DeepSeek Harness and need to scan new plugins for security risks, this tool can provide help. For users who only use pre-verified plugins, this tool is not necessary.

Watch out — Sandbox test passed: Installed in a new profile and registered into the profile by harness. No obvious issues found.

The verdict — I would install it because it can check DSH-specific attack surfaces, but the premise is to use static scan mode.

What it is — dsh-webui-auth enforces four-layer authentication at the HTTP/transport layer for DeepSeek Harness WebUI.

Who it is for — In scenarios where DeepSeek Harness WebUI requires multi-user protection for sensitive data, it is suitable to install this plugin. If the WebUI is used solely for personal debugging or display purposes, this plugin is not necessary.

Watch out — npm installation uses a pure JS package with no build step required. After upgrading DeepSeek Harness, an extra restart is needed for the patch to take effect. Sessions are stored in process memory and will be lost after restart.

The verdict — I would install it because it forces authentication at the transport layer that browsers cannot bypass via developer tools. The premise is accepting the cost of session loss after restarts.

What it is — DeepSeek Harness Web authentication gateway plugin, supporting password and TOTP 2FA authentication.

Who it is for — In scenarios requiring remote access to DeepSeek Harness Web, people lacking authentication layer when using DeepSeek Harness for web work are suitable to install it. People not using external ports are not suitable to install it, because the plugin uses external ports for authentication.

Watch out — Sandbox test passed: installed in a new profile and registered into the profile by harness. No obvious pitfalls found.

The verdict — I would install it, because it complements the authentication layer for dsh web.

What it is — It adds a model-based permission approval mode to DeepSeek Harness, answering approval requests with a separate reviewer model in a specific preset.

Who it is for — It is suitable for users who need an independent model to answer permission requests when using DeepSeek Harness. Users who want to stick to pure human approval are not necessary to install it, because they can choose other presets.

Watch out — Sandbox test passed. It was registered into the harness profile after installation in a fresh profile. No obvious issues found.

The verdict — I would install it if I need model-assisted approval because it provides fail-to-human handling.

What it is — upstream-radar tracks exact dependency paths of DSH plugins, OSV vulnerability signals, and npm release changes, then routes project evidence to a DSH Agent.

Who it is for — When a DSH profile contains multiple third-party bundles at once, monitoring dependency security becomes necessary. Profiles that use only one built-in plugin or zero third-party bundles do not need this plugin.

Watch out — Manually allow the build script when installing from source. It executes shell commands. Sandbox testing confirmed successful registration in a fresh profile; no obvious issues found.

The verdict — I would install it because it supplies dependency-path analysis for profiles that contain more than one bundle.

What it is — Adds Auto Approve permission preset to DeepSeek Harness Web UI.

Who it is for — Suitable for users handling approval requests in the DeepSeek Harness Web UI. When not selecting the Auto Approve permission preset, the plugin does not process approval/request.

Watch out — Tested in a fresh profile and registered to the profile. No obvious pitfalls found.

The verdict — I would install it because it uses a restricted Reviewer Agent to review each approval request.

What it is — DeepSeek Harness plugin that predicts sandbox operation risks with Flash model, auto-approving repeatable actions and routing risky ones to human review.

Who it is for — When running automated tasks in DeepSeek Harness sandbox environment using Flash model, the plugin helps by predicting if confirmation is needed. Users who do not perform sandboxed operations or do not use Flash for risk prediction do not need this plugin.

Watch out — Configuration involves adding auto-approve preset to ~/.dsh/profiles/web/cordis.patch.yml, followed by restarting dsh web and selecting the preset. Sandbox testing succeeded after installing in a fresh profile and registering the plugin with harness. No obvious issues detected.

The verdict — I would install it to reduce manual approvals for sandbox tasks via Flash prediction, provided the cordis.patch.yml preset is configured first.

What it is — DSH Verification Receipt records tool counts and verification signals for each durable turn/end and writes summaries to a local JSONL file.

Who it is for — If you need to record tool counts and verification signals during DeepSeek Harness agent tasks, you can install this plugin. If your work does not involve generating execution summaries, you can skip installing this plugin.

Watch out — Sandbox test passed: the plugin was installed in a fresh profile and registered by harness. No obvious issues found. Compatibility check passed.

The verdict — I would not install it if the goal is to prove that tests ran or that code is correct, because it only records execution traces and does not provide semantic proof.

What it is — DeepSeek Harness plugin, listens to tool results and session events, appends hash-chained JSONL evidence receipts.

Who it is for — If you need to audit tool calls and session events in a DeepSeek Harness profile. If you are not using DeepSeek Harness for tool calls and session events, you can skip installing it.

Watch out — No obvious issues found. Sandbox test passed, it was installed in a new profile and registered into harness.

The verdict — I would install it because it provides local auditable receipts without storing sensitive data.