← Back to Scanner

xlsx Security Audit Report

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

xlsx is an AI agent skill. ClawSecure audited xlsx across 54 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 63/100 (Medium Risk). The 4 findings concentrate in Command Injection, Code Injection and Permissions Manifest, including Dangerous combination of code execution and system commands… and Potentially dangerous code pattern detected: system\(. 2 were rated high or critical severity.

Is xlsx safe?

ClawSecure audited xlsx and assigned a security score of 63/100 (Medium Risk), identifying 4 findings across Command Injection and Code Injection. Review the findings below before installing.

What did ClawSecure find in xlsx?

ClawSecure identified 4 findings in xlsx, concentrated in Command Injection, Code Injection and Permissions Manifest. 2 were rated high or critical severity. The most severe include Dangerous combination of code execution and system commands… and Potentially dangerous code pattern detected: system\(.

How was xlsx audited?

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

What does a score of 63 mean?

ClawSecure assigned xlsx a security score of 63/100, placing it in the Medium Risk range. This reflects 4 findings led by Command 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 xlsx

ClawSecure detected 4 security findings in xlsx, spanning Command Injection, Code Injection, Permissions Manifest and Obfuscation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for xlsx

Harden command execution
xlsx 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.
Eliminate dynamic code execution
xlsx 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.
Review obfuscated or hidden code
xlsx contains obfuscated or hidden content that resists review. Inspect encoded, minified or hidden files to confirm they are not concealing unexpected behavior before installing.

Related Security Research

Why Generic Scanners Fail at AI Agent SecurityUnderstanding Our 3-Layer Audit ProtocolBeyond Static Scans: Why ClawSecure Verifies Agentic Intent

Related AI Agent Security Audits

docxScore 68/100@penpot/mcpScore 75/100gitlab-cli-skillsScore 55/100devops-mainScore 75/100devops-mainScore 75/100

Scanned on July 29, 2026. xlsx 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