What it may solve
Control how the DeepSeek Harness Web GUI is reachable: local only, Tailscale, all local networks, or off.
Imported third-party catalog description; not a Registry verification conclusion.Control how the DeepSeek Harness Web GUI is reachable: local only, Tailscale, all local networks, or off.
Author: czhzz · Remote & Mobile · Catalog snapshot: 2026-09-19Canonical semantic path
Control how the DeepSeek Harness Web GUI is reachable: local only, Tailscale, all local networks, or off.
Imported third-party catalog description; not a Registry verification conclusion.— stars · 0 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 4/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository is reachable and not archived. Public data: 0 stars, 13 commits, 0 forks, and 0 watches; latest commit 2026-09-17.
Conclusion: Resolved npm release 0.1.2, published 2026-09-17, license MIT.
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 1 code capabilities: may access the network. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-net-access@0.1.2; SHA-256: b24ca184722948a017b27577853b71d4ec651ceb442afb8673e5822166ee7261.
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-net-access. 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-net-accessAnalyzed 0.1.2github:czhzz/dsh-net-accessExact version not resolved