jira-read-ticket Security Audit Report
jira-read-ticket is an AI agent skill. ClawSecure audited jira-read-ticket across 6 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 10/100 (High Risk). The 14 findings concentrate in Data Exfiltration, Code Injection and Resource Abuse, including Suspicious Pattern: while True: and Suspicious Pattern: while True:. 5 were rated high or critical severity.
Is jira-read-ticket safe?
ClawSecure audited jira-read-ticket and assigned a security score of 10/100 (High Risk), identifying 14 findings across Data Exfiltration and Code Injection. Review the findings below before installing.
What did ClawSecure find in jira-read-ticket?
ClawSecure identified 14 findings in jira-read-ticket, concentrated in Data Exfiltration, Code Injection and Resource Abuse. 5 were rated high or critical severity. The most severe include Suspicious Pattern: while True: and Suspicious Pattern: while True:.
How was jira-read-ticket audited?
ClawSecure ran jira-read-ticket through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 6 files.
What does a score of 10 mean?
ClawSecure assigned jira-read-ticket a security score of 10/100, placing it in the High Risk range. This is driven by 14 findings led by Data Exfiltration that should be addressed before use. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).
Audit Findings for jira-read-ticket
ClawSecure detected 14 security findings in jira-read-ticket, spanning Data Exfiltration, Code Injection, Resource Abuse and Unauthorized Tool Use.
- high · Suspicious Pattern: while True:. Resource Abuse finding detected in
scripts/fetch_assigned_tickets.py:152. - high · Suspicious Pattern: while True:. Resource Abuse finding detected in
scripts/fetch_comments.py:75. - high · Potentially dangerous code pattern detected: base64.*decode. Code Injection finding detected in
fetch_assigned_tickets.py. - high · Potentially dangerous code pattern detected: base64.*decode. Code Injection finding detected in
fetch_comments.py. - high · Potentially dangerous code pattern detected: base64.*decode. Code Injection finding detected in
fetch_description.py. - medium · Undeclared Network Access. Unauthorized Tool Use finding detected in
SKILL.md. - medium · Suspicious Pattern: urllib.request.Request(. Data Exfiltration finding detected in
scripts/fetch_assigned_tickets.py:53. - medium · Suspicious Pattern: urllib.request.urlopen(. Data Exfiltration finding detected in
scripts/fetch_assigned_tickets.py:55. - medium · Suspicious Pattern: urllib.request.Request(. Data Exfiltration finding detected in
scripts/fetch_comments.py:44. - medium · Suspicious Pattern: urllib.request.urlopen(. Data Exfiltration finding detected in
scripts/fetch_comments.py:50. - medium · Suspicious Pattern: urllib.request.Request(. Data Exfiltration finding detected in
scripts/fetch_description.py:47. - medium · Suspicious Pattern: urllib.request.urlopen(. Data Exfiltration finding detected in
scripts/fetch_description.py:53.
Showing the 12 highest-severity of 14 findings. The full interactive list appears below.
3-Layer Audit Protocol
Security Recommendations for jira-read-ticket
Audit external network connections
Eliminate dynamic code execution
Add a config.json permissions manifest
Related Security Research
ClawHavoc Explained: The Malware Family Targeting AI Agents→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→Related AI Agent Security Audits
Scanned on March 19, 2026. jira-read-ticket is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.