← Back to Scanner

officecli Security Audit Report

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

officecli is an AI agent skill. ClawSecure audited officecli across 1 file through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 83/100 (Safe). The 4 findings concentrate in Code Injection, Permissions Manifest and Command Injection, including Potentially dangerous code pattern detected: curl.*\|.*sh and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is officecli safe?

ClawSecure audited officecli and assigned a security score of 83/100 (Safe), identifying 4 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in officecli?

ClawSecure identified 4 findings in officecli, concentrated in Code Injection, Permissions Manifest and Command Injection. 1 was rated high or critical severity. The most severe include Potentially dangerous code pattern detected: curl.*\|.*sh and Missing config.json - agent may not be properly configured.

How was officecli audited?

ClawSecure ran officecli through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 1 file.

What does a score of 83 mean?

ClawSecure assigned officecli a security score of 83/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status, though 1 finding was rated high or critical and warrants review. 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 officecli

ClawSecure detected 4 security findings in officecli, spanning Code Injection, Permissions Manifest, Command Injection and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for officecli

Eliminate dynamic code execution
officecli 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.
Harden command execution
officecli 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.
Resolve policy violations
officecli trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.

Related Security Research

Why Generic Scanners Fail at AI Agent SecurityBeyond Static Scans: Why ClawSecure Verifies Agentic IntentHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

a2aScore 85/100devops-mainScore 75/100TestFilesScore 95/100devops-mainScore 75/100devops-mainScore 75/100

Scanned on June 12, 2026. officecli 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