← Back to Scanner

azure-cli Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

azure-cli is an AI agent skill, created by ddevaal and published at openclaw/skills. ClawSecure audited azure-cli across 9 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 75/100 (Medium Risk). The 3 findings concentrate in Code Injection and Permissions Manifest, including Potentially dangerous code pattern detected: curl.*\|.*sh and Potentially dangerous code pattern detected: curl.*\|.*sh. 2 were rated high or critical severity.

Is azure-cli safe?

ClawSecure audited azure-cli and assigned a security score of 75/100 (Medium Risk), identifying 3 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in azure-cli?

ClawSecure identified 3 findings in azure-cli, concentrated in Code Injection and Permissions Manifest. 2 were rated high or critical severity. The most severe include Potentially dangerous code pattern detected: curl.*\|.*sh and Potentially dangerous code pattern detected: curl.*\|.*sh.

How was azure-cli audited?

ClawSecure ran azure-cli through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 9 files from openclaw/skills.

What does a score of 75 mean?

ClawSecure assigned azure-cli a security score of 75/100, placing it in the Medium Risk range. This reflects 3 findings led by Code Injection 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 azure-cli

ClawSecure detected 3 security findings in azure-cli, spanning Code Injection and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for azure-cli

Eliminate dynamic code execution
azure-cli evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.
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.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

oh-my-claudecodeScore 80/100opencode-auto-continueScore 90/100shodan-skillScore 90/100clawdhubScore 85/100a2aScore 85/100

Scanned on February 7, 2026. azure-cli 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