← Back to Scanner

docx Security Audit Report

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

docx is an AI agent skill. ClawSecure audited docx across 62 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 68/100 (Medium Risk). The 5 findings concentrate in Supply Chain Attack, Command Injection and Permissions Manifest, including An archive is extracted and its contents are then executed.… and An archive is extracted and its contents are then executed.…. 2 were rated high or critical severity.

Is docx safe?

ClawSecure audited docx and assigned a security score of 68/100 (Medium Risk), identifying 5 findings across Supply Chain Attack and Command Injection. Review the findings below before installing.

What did ClawSecure find in docx?

ClawSecure identified 5 findings in docx, concentrated in Supply Chain Attack, Command Injection and Permissions Manifest. 2 were rated high or critical severity. The most severe include An archive is extracted and its contents are then executed.… and An archive is extracted and its contents are then executed.….

How was docx audited?

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

What does a score of 68 mean?

ClawSecure assigned docx a security score of 68/100, placing it in the Medium Risk range. This reflects 5 findings led by Supply Chain Attack 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 docx

ClawSecure detected 5 security findings in docx, spanning Supply Chain Attack, Command Injection, Permissions Manifest and Obfuscation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for docx

Harden command execution
docx 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.
Review obfuscated or hidden code
docx contains obfuscated or hidden content that resists review. Inspect encoded, minified or hidden files to confirm they are not concealing unexpected behavior before installing.
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→Understanding Our 3-Layer Audit Protocol→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

xlsxScore 63/100@penpot/mcpScore 75/100gitlab-cli-skillsScore 55/100devops-mainScore 75/100devops-mainScore 75/100

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