What it may solve
Jira tools for DeepSeek Harness: search issues and users, inspect projects/types/priorities, manage tickets, comments, and transitions
Imported third-party catalog description; not a Registry verification conclusion.Jira tools for DeepSeek Harness: search issues and users, inspect projects/types/priorities, manage tickets, comments, and transitions
Author: LJH-snow · Tools & Capabilities · Catalog snapshot: 2026-09-19Canonical semantic path
Jira tools for DeepSeek Harness: search issues and users, inspect projects/types/priorities, manage tickets, comments, and transitions
Imported third-party catalog description; not a Registry verification conclusion.— stars · 96 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, 2 commits, 0 forks, and 0 watches; latest commit 2026-08-29.
Conclusion: Resolved npm release 0.2.0, published 2026-08-29, 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: 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: @libai168/dsh-tool-jira@0.2.0; SHA-256: dc69e0ad327dcffad2db002ee80979202db3f64bc050fe721d00a8c59280d892.
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-jira. 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-jiraAnalyzed 0.2.0github:LJH-snow/dsh-tool-jiraExact version not resolved