What it may solve
保险区 Vault Wall — 让 DeepSeek Harness 无法感知、无法触碰用户指定敏感路径的隔离墙Plugin(隔离墙 + 人在回路审批 + 执行后验证 + 循环纠正 + 可回滚规则)
Imported third-party catalog description; not a Registry verification conclusion.保险区 Vault Wall — 让 DeepSeek Harness 无法感知、无法触碰用户指定敏感路径的隔离墙Plugin(隔离墙 + 人在回路审批 + 执行后验证 + 循环纠正 + 可回滚规则)
Author: lxwallac · Security & Permissions · Catalog snapshot: 2026-09-19Canonical semantic path
保险区 Vault Wall — 让 DeepSeek Harness 无法感知、无法触碰用户指定敏感路径的隔离墙Plugin(隔离墙 + 人在回路审批 + 执行后验证 + 循环纠正 + 可回滚规则)
Imported third-party catalog description; not a Registry verification conclusion.— stars · 1370 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.
Source structure has not been analyzed.
Repository metadata has not been analyzed.
npm release metadata has not been analyzed.
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The scan observed 2 code capabilities: may read environment variables, may create or modify files. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-vault-wall@0.4.0; SHA-256: 9da4f79b5436402862e4e9c9a097d368b502576887e89e0d16e0ba70e5fc9d68.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention dsh-vault-wall. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
dsh-vault-wallAnalyzed 0.4.0github:lxwallac/dsh-vault-wallExact version not resolved