What it may solve
Sleev routing observability for DeepSeek Harness
Imported third-party catalog description; not a Registry verification conclusion.Sleev routing observability for DeepSeek Harness
Author: xarleyn · Memory · Catalog snapshot: 2026-09-19Canonical semantic path
Sleev routing observability for DeepSeek Harness
Imported third-party catalog description; not a Registry verification conclusion.— stars · 153 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 archived. Public data: 0 stars, 10 commits, 0 forks, and 0 watches; latest commit 2026-09-06.
Conclusion: Resolved npm release 0.0.1, published 2026-08-27, 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 3 code capabilities: declares a prepare script, normally used when building or publishing the package, 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: dsh-sleev@0.0.1; SHA-256: 0011798de212366bbed312c41b37c0b4f3a31e52202ee56c364045914a047eee.
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-sleev. 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-sleevAnalyzed 0.0.1github:xarleyn/dsh-sleevExact version not resolved