What it may solve
Local, read-only usage and performance analytics for DeepSeek Harness sessions.
Imported third-party catalog description; not a Registry verification conclusion.Local, read-only usage and performance analytics for DeepSeek Harness sessions.
Author: faz4hu · Sessions & Messages · Catalog snapshot: 2026-09-19Canonical semantic path
Local, read-only usage and performance analytics for DeepSeek Harness sessions.
Imported third-party catalog description; not a Registry verification conclusion.— stars · 478 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 could not be confirmed as reachable.
Conclusion: Resolved npm release 0.2.0, published 2026-08-17, 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 1 code capabilities: 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-usage-insights@0.2.0; SHA-256: 75d70cf72beab28e12990119ee07e97044e6a69f55bb03529004ca20c7b32ef2.
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-usage-insights. 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-usage-insightsAnalyzed 0.2.0github:faz4hu/dsh-usage-insightsExact version not resolved