← Back to Scanner

"git-commit-update-jira-story" Security Audit Report

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

"git-commit-update-jira-story" is an AI agent skill. ClawSecure audited "git-commit-update-jira-story" across 6 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 0/100 (High Risk). The 11 findings concentrate in Data Exfiltration, Command Injection and Unauthorized Tool Use, including Credential Harvesting via Network and Multi-File Data Exfiltration Chain. 4 were rated high or critical severity.

Is "git-commit-update-jira-story" safe?

ClawSecure audited "git-commit-update-jira-story" and assigned a security score of 0/100 (High Risk), identifying 11 findings across Data Exfiltration and Command Injection. Review the findings below before installing.

What did ClawSecure find in "git-commit-update-jira-story"?

ClawSecure identified 11 findings in "git-commit-update-jira-story", concentrated in Data Exfiltration, Command Injection and Unauthorized Tool Use. 4 were rated high or critical severity. The most severe include Credential Harvesting via Network and Multi-File Data Exfiltration Chain.

How was "git-commit-update-jira-story" audited?

ClawSecure ran "git-commit-update-jira-story" through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 6 files.

What does a score of 0 mean?

ClawSecure assigned "git-commit-update-jira-story" a security score of 0/100, placing it in the High Risk range. This is driven by 11 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 "git-commit-update-jira-story"

ClawSecure detected 11 security findings in "git-commit-update-jira-story", spanning Data Exfiltration, Command Injection, Unauthorized Tool Use and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for "git-commit-update-jira-story"

Audit external network connections
"git-commit-update-jira-story" 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.
Harden command execution
"git-commit-update-jira-story" constructs or runs system commands. Validate that commands are built only from trusted inputs, never pass user-controlled strings directly to a shell, and restrict execution to an allow-list of expected commands.
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

byterover-cliScore 0/100explain-code-for-developerScore 0/100explain-code-for-developerScore 0/100explain-code-for-developerScore 0/100explain-code-for-developerScore 0/100

Scanned on June 12, 2026. "git-commit-update-jira-story" 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