← Back to Scanner

kleo-static-files Security Audit Report

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

kleo-static-files is an AI agent skill, created by awaaate and published at openclaw/skills. ClawSecure audited kleo-static-files across 4 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 4 findings concentrate in Code Injection, Policy Violation 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 kleo-static-files safe?

ClawSecure audited kleo-static-files and assigned a security score of 75/100 (Medium Risk), identifying 4 findings across Code Injection and Policy Violation. Review the findings below before installing.

What did ClawSecure find in kleo-static-files?

ClawSecure identified 4 findings in kleo-static-files, concentrated in Code Injection, Policy Violation 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 kleo-static-files audited?

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

What does a score of 75 mean?

ClawSecure assigned kleo-static-files a security score of 75/100, placing it in the Medium Risk range. This reflects 4 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 kleo-static-files

ClawSecure detected 4 security findings in kleo-static-files, spanning Code Injection, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for kleo-static-files

Eliminate dynamic code execution
kleo-static-files 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.
Resolve policy violations
kleo-static-files trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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→OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→

Related AI Agent Security Audits

clawgo-upload-1.0.0Score 85/100clawgo-uploadScore 86/100clawgo-uploadScore 86/100clawgo-uploadScore 86/100clawgo-uploadScore 86/100

Scanned on February 7, 2026. kleo-static-files 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