What it may solve
Fail-closed password authentication proxy bundle for the DeepSeek Harness Web profile
Imported third-party catalog description; not a Registry verification conclusion.Fail-closed password authentication proxy bundle for the DeepSeek Harness Web profile
Author: taichuy · Tools & Capabilities · Catalog snapshot: 2026-09-19Canonical semantic path
Fail-closed password authentication proxy bundle for the DeepSeek Harness Web profile
Imported third-party catalog description; not a Registry verification conclusion.— stars · 2345 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 5/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: 27 stars, 13 commits, 5 forks, and 0 watches; latest commit 2026-08-16.
Conclusion: Resolved npm release 0.4.1, published 2026-08-16, license MIT.
Conclusion: Compatibility verification did not pass: the DSH process kept running but did not become healthy within the observation window. 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 3 code capabilities: may read environment variables, may create or modify files, 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: deepseek-harness-auth@0.4.1; SHA-256: d14a0460bf83b191d506c546eaf08e46722d86b4e1d3b275c3aaf341e9ee8350.
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 deepseek-harness-auth. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
deepseek-harness-authAnalyzed 0.4.1github:taichuy/deepseek-harness-authExact version not resolved