What it may solve
Kubernetes tools for DeepSeek Harness: cluster, namespace, workload, pod, log, rollout, and manifest operations
Imported third-party catalog description; not a Registry verification conclusion.Kubernetes tools for DeepSeek Harness: cluster, namespace, workload, pod, log, rollout, and manifest operations
Author: LJH-snow · Tools & Capabilities · Catalog snapshot: 2026-09-19Canonical semantic path
Kubernetes tools for DeepSeek Harness: cluster, namespace, workload, pod, log, rollout, and manifest operations
Imported third-party catalog description; not a Registry verification conclusion.— stars · 116 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: 0 stars, 1 commits, 0 forks, and 0 watches; latest commit 2026-08-27.
Conclusion: Resolved npm release 0.1.0, published 2026-08-28, 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 2 code capabilities: declares a prepare script, normally used when building or publishing the package, 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: @libai168/dsh-tool-kubernetes@0.1.0; SHA-256: 52c4a772d473b2336c59fbb2d7729f1259136186dd24afe5f0a5a545f27e65e7.
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 @libai168/dsh-tool-kubernetes. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@libai168/dsh-tool-kubernetesAnalyzed 0.1.0github:LJH-snow/dsh-tool-kubernetesExact version not resolved