← Back to Scanner

jira Security Audit Report

πŸ”­ Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

jira is an AI agent skill. ClawSecure audited jira across 5 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 50/100 (Medium Risk). The 9 findings concentrate in Data Exfiltration, Policy Violation and Unauthorized Tool Use, including Suspicious Pattern: fs.readFileSync( and Suspicious Pattern: fs.readFileSync(. 2 were rated high or critical severity.

Is jira safe?

ClawSecure audited jira and assigned a security score of 50/100 (Medium Risk), identifying 9 findings across Data Exfiltration and Policy Violation. Review the findings below before installing.

What did ClawSecure find in jira?

ClawSecure identified 9 findings in jira, concentrated in Data Exfiltration, Policy Violation and Unauthorized Tool Use. 2 were rated high or critical severity. The most severe include Suspicious Pattern: fs.readFileSync( and Suspicious Pattern: fs.readFileSync(.

How was jira audited?

ClawSecure ran jira through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 5 files.

What does a score of 50 mean?

ClawSecure assigned jira a security score of 50/100, placing it in the Medium Risk range. This reflects 9 findings led by Data Exfiltration that warrant review before production 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

ClawSecure detected 9 security findings in jira, spanning Data Exfiltration, Policy Violation, Unauthorized Tool Use and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for jira

Audit external network connections
jira sends data to external endpoints. Confirm each destination is expected and authorized, and remove any callback that exfiltrates data. ClawSecure monitors for known exfiltration and C2 endpoints.
Resolve policy violations
jira trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.

Related Security Research

ClawHavoc Explained: The Malware Family Targeting AI Agents→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→

Related AI Agent Security Audits

tradingview-mcpScore 55/100tradingview-mcpScore 55/100tradingview-mcpScore 55/100playwright-best-practicesScore 63/100neckr0ik-polymarket-traderScore 55/100

Scanned on June 12, 2026. jira is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan