Per-model proxy routing for LLM requests: selected models go through a proxy (Clash etc.) while the rest stay direct, with automatic retry on transport errors, 429 and 5xx, configured live from the settings page.
Author: superfish058 · Models & Providers · Catalog snapshot: 2026-09-19Canonical semantic path
Per-model proxy routing for LLM requests: selected models go through a proxy (Clash etc.) while the rest stay direct, with automatic retry on transport errors, 429 and 5xx, configured live from the settings page.
Imported third-party catalog description; not a Registry verification conclusion.5 stars · 1648 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.
Source structure has not been analyzed.
Repository metadata has not been analyzed.
npm release metadata has not been analyzed.
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 4 code capabilities: declares a prepare script, normally used when building or publishing the package, contains credential or token handling code, may read environment variables, 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: @superfish058/dsh-llm-proxy@1.4.0; SHA-256: ae45a315e89f459e878dc64d4589a9f2dd7ea4a969b3a989b18667f96fb7c7f9.
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-llm-proxy. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@superfish058/dsh-llm-proxyAnalyzed 1.4.0github:superfish058/dsh-llm-proxyExact version not resolved