01
QUICK ANSWER
What is the dsh-security-audit plugin?
Local security audit: config, plugin origins, sessions, network exposure — read-only redacted risk report.
Learn what dsh-security-audit does, decide whether it fits a DeepSeek Harness workflow, and find the verified upstream installation path.
- Plugin type
- Security & Permissions
- Install target
- DeepSeek Harness
- Upstream
- @omdsh-dev
02
CORE FEATURES
dsh-security-audit plugin features
The capabilities below are derived from the upstream description captured for dsh-security-audit. Use them to compare the plugin with other security & permissions options before installation.
Local security audit
config, plugin origins, sessions, network exposure — read-only redacted risk report
03
USE CASES
dsh-security-audit use cases
dsh-security-audit is most relevant when a DeepSeek Harness workflow needs one or more of these security & permissions outcomes.
Review high-impact actions
Audit tool permissions
Detect risky configuration
04
INSTALLATION
How to install dsh-security-audit
Review the repository and the command in its current README before execution. The command below was captured from the public directory or the maintainer documentation.
dsh plugin --profile web add github:omdsh-dev/dsh-security-audit- InspectRead the repository, dependencies and requested configuration.
- InstallRun the command for the intended DSH profile.
- Restart & verifyRestart Harness and test in a disposable workspace.
Run the upstream installation command for the intended profile, restart that DeepSeek Harness process, and confirm the plugin appears before granting it access to a real project.
If you are new to plugin profiles, read the DeepSeek Harness installation guide before changing an active environment.
05
SOURCE & SAFETY
dsh-security-audit GitHub repository and safety
GitHub repositoryhttps://github.com/omdsh-dev/dsh-security-auditThis is third-party code that can run with your local permissions. Review the repository, dependencies, install scripts, network access and requested credentials; pin a commit when reproducibility matters.
Registry sourced means the name, description and install path were taken from public project records. It does not mean this site completed a runtime test or security audit.
The record was last checked on 2026-08-19. Reconfirm the current README, release notes and requested permissions because upstream behavior can change after this snapshot.