What it may solve
Unofficial ChatGPT OAuth provider for DeepSeek Harness with strict native OS keychain storage
Imported third-party catalog description; not a Registry verification conclusion.Unofficial ChatGPT OAuth provider for DeepSeek Harness with strict native OS keychain storage
Author: CpfPatrick · Memory · Catalog snapshot: 2026-09-19Canonical semantic path
Unofficial ChatGPT OAuth provider for DeepSeek Harness with strict native OS keychain storage
Imported third-party catalog description; not a Registry verification conclusion.— stars · 190 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: 2 stars, 3 commits, 0 forks, and 0 watches; latest commit 2026-08-15.
Conclusion: Resolved npm release 0.1.0-alpha.1, published 2026-08-15, 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 5 code capabilities: contains credential or token handling code, may read environment variables, may create or modify files, may access the network, may start external processes. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-codex-keychain@0.1.0-alpha.1; SHA-256: a3126cbe4b95b486775ed7af30e63a66857687ae252a214cce9361340cdbc147.
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-codex-keychain. 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-codex-keychainAnalyzed 0.1.0-alpha.1github:CpfPatrick/dsh-codex-keychainExact version not resolved