What it may solve
DSH plugin for static OpenAI Chat Completions, OpenAI Responses, and Anthropic Messages providers
Imported third-party catalog description; not a Registry verification conclusion.DSH plugin for static OpenAI Chat Completions, OpenAI Responses, and Anthropic Messages providers
Author: linziyanleo · Tools & Capabilities · Catalog snapshot: 2026-09-19Canonical semantic path
DSH plugin for static OpenAI Chat Completions, OpenAI Responses, and Anthropic Messages providers
Imported third-party catalog description; not a Registry verification conclusion.linziyanleo/dsh-custom-provider
— stars · 1008 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, 19 commits, 0 forks, and 0 watches; latest commit 2026-08-19.
Conclusion: Resolved npm release 0.1.4, published 2026-08-19, 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: @linziyanleo/dsh-custom-provider@0.1.4; SHA-256: bc541ca66fe7f3ea5690ae3b508d79b8001289b4444067ec0101fab9eeb52b74.
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 @linziyanleo/dsh-custom-provider. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@linziyanleo/dsh-custom-providerAnalyzed 0.1.4github:linziyanleo/dsh-custom-providerExact version not resolved