Dsh Security Audit

by omdsh-dev · omdsh-dev/dsh-security-audit

Build failsBundlegit (build fails)freshinstall scripts

DSH 本机安全审计插件：配置/插件来源/会话/网络暴露面，只读脱敏风险报告

Install Dsh Security Audit

Likely fails to load: not on npm, needs a build, and ships no `prepare` script — a git install fetches sources, not built artifacts, so the entry point is never produced.

This install is expected to fail

A git install pulls source, not build output. This package needs a build step, has no prepare script to run it, and is not published to npm — so nothing produces the compiled output the loader then goes looking for.

Three things would fix it, all of them on the author's side: publish the package to npm, add a prepare script that builds on install, or commit the build output to the repository. Until one of those happens, the command below is here so you can reproduce the failure, not so you can install it.

What would be run — expected to install and then fail to load

# 1. add the bundle to a profile — --profile my-profile points at $DSH_HOME/profiles/my-profile
dsh plugin --profile my-profile add github:omdsh-dev/dsh-security-audit

# 2. verify: the bundle should show up as a layer in the resolved config
dsh --profile my-profile --dump-config

# 3. boot the profile
dsh --profile my-profile

Before you run itinstall scripts

This package declares prepack — package-manager lifecycle scripts that execute on your machine at install time, outside the agent sandbox, before any tool-approval prompt exists.
A plugin runs with your permissions once loaded: it can read your files, use your credentials and reach the network. Tool approvals do not sandbox it.
Installing from git resolves a moving branch. Pin a commit — github:omdsh-dev/dsh-security-audit#<commit-sha> — so the code you reviewed is the code you install.

Prerequisites

API key: Not required.
Network access: Not required at runtime.
Language: TypeScript — a git install pulls this source, not build output.

Install check

Every field the verdict was derived from, so you can re-derive it yourself

Field checked	Result	Weight	What the spec says about it
lifecycleScripts	fail	warn	runs at install time, outside the agent sandbox: prepack
dsh.bundle	pass	fatal	package.json declares a `dsh.bundle` layer
dsh.bundle.patch file	pass	fatal	patch file present at `cordis.patch.yml`
npm registry	missing	warn	`@deepseek-ai/dsh-security-audit` is not published to npm
prepare script	missing	fatal	needs a build but ships no `prepare` script — a git install fetches sources, not built artifacts

Verdict reason: git-only + needs build + no prepare script
package.json read: package.json
Rules applied from: docs/user/develop/basic/publish.md
Checked at: 2026-08-15
Install-time scripts: prepack

From the README

Excerpt as published by the author, plain text, unedited

DSH 本机安全审计插件 —— 防御性、只读的安全审计：配置、凭据存储元数据、已安装插件来源、关键路径权限、会话文件结构与网络暴露面。输出脱敏、可复现、可定位的风险报告。仓库：[https://github.com/omdsh-dev/dsh-security-audit](https://github.com/omdsh-dev/dsh-security-audit)（public） DSH 本地环境承载 API Key、token、会话内容和插件加载边界，误配置（服务监听公网、凭据文件权限过宽、插件来源不可信、会话文件结构异常）会造成真实风险。现有工具没有这个视角： 1. **`plugin-check` 只做结构/合规检查**——不评估凭据暴露面、危险能力和路径逃逸 2. **`session-health` 只做健康诊断**——不涉及来源可信度与安全风险裁定 3. **手工排查不可复现**——凭据位置、权限、监听端口、插件来源分散在多处，逐项人工检查极易遗漏且无法留档本插件以只读方式审计本机 DSH 环境并输出风险报告：**不自动修复、不连接远程、不执行被审计插件、不把"没读到"当作"安全"**。 - **只读**：绝不修改/删除任何文件，绝不执行被审计插件的代码，绝不主动连接远程目标 - **秘密脱敏**：疑似秘密只返回类型 / 长度 / 进程内随机 HMAC fingerprint / 路径 / 行号，**完整值永不出现在 canonical 输出**（设计级保证，非截断） - **路径围栏**：所有路径经 lstat → realpath → containment 检查；`root` 固定为进程启动时解析的 `$DSH_HOME`（或管理员声明的 allowedRoot），模型参数不能扩大读取范围 - **诚实判定**：finding / pass /