What it may solve
DSH Plugin(用量中心):常驻用量卡片 · 多提供方用量/余额查询(OpenCode Go 订阅 + DeepSeek 余额 + Command Code 订阅/余额,对齐 cc-switch 查询语义)
Imported third-party catalog description; not a Registry verification conclusion.DSH Plugin(用量中心):常驻用量卡片 · 多提供方用量/余额查询(OpenCode Go 订阅 + DeepSeek 余额 + Command Code 订阅/余额,对齐 cc-switch 查询语义)
Author: loommii · Usage & Billing · Catalog snapshot: 2026-09-19Canonical semantic path
DSH Plugin(用量中心):常驻用量卡片 · 多提供方用量/余额查询(OpenCode Go 订阅 + DeepSeek 余额 + Command Code 订阅/余额,对齐 cc-switch 查询语义)
Imported third-party catalog description; not a Registry verification conclusion.— stars · 786 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: contains credential or token handling code, 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: @loommii/dsh-provider-usage@0.13.0; SHA-256: f27559f99e85afaea7613fba3fc8d663d4034cfb05371a423087d101240f1272.
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 @loommii/dsh-provider-usage. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@loommii/dsh-provider-usageAnalyzed 0.13.0github:loommii/dsh-provider-usageExact version not resolved