What it may solve
Provider-neutral account authorization UI for DeepSeek Harness
Imported third-party catalog description; not a Registry verification conclusion.Provider-neutral account authorization UI for DeepSeek Harness
Author: lxy271713 · UI Enhancements · Catalog snapshot: 2026-09-19Canonical semantic path
Provider-neutral account authorization UI for DeepSeek Harness
Imported third-party catalog description; not a Registry verification conclusion.lxy271713/dsh-account-authorization
— stars · 0 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: 1 stars, 5 commits, 0 forks, and 0 watches; latest commit 2026-08-31.
Conclusion: Resolved npm release 0.1.0, published 2026-08-31, 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 2 code capabilities: contains credential or token handling code, 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-account-authorization@0.1.0; SHA-256: a2dd087f0a0d7b0292b316c5a9eb1b81957126f7c59b75274519c4a47f2de570.
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-account-authorization. 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-account-authorizationAnalyzed 0.1.0github:lxy271713/dsh-account-authorizationExact version not resolved