What it may solve
Kimi Code written in DSH form: the Kimi Code CLI 0.39.1 tool surface registered as DSH tools.
Imported third-party catalog description; not a Registry verification conclusion.Kimi Code written in DSH form: the Kimi Code CLI 0.39.1 tool surface registered as DSH tools.
Author: oppnc · Tools & Capabilities · Catalog snapshot: 2026-09-19Canonical semantic path
Kimi Code written in DSH form: the Kimi Code CLI 0.39.1 tool surface registered as DSH tools.
Imported third-party catalog description; not a Registry verification conclusion.— stars · 0 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: 3 stars, 12 commits, 0 forks, and 0 watches; latest commit 2026-08-31.
Conclusion: Resolved npm release 0.1.8, published 2026-08-31, 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 5 code capabilities: contains credential or token handling code, may read environment variables, may create or modify files, may access the network, may start external processes. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-kernel-kimi@0.1.8; SHA-256: 7f6105c38a065430bfba1edce6e869ed9d9828330a0bb689bca75800ca266d50.
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-kernel-kimi. 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-kernel-kimiAnalyzed 0.1.8github:oppnc/dsh-kernel-kimiExact version not resolved