← Back to Scanner

fast-io Security Audit Report

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

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

Is fast-io safe?

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

What did ClawSecure find in fast-io?

ClawSecure identified 4 findings in fast-io, concentrated in Code Injection, Command Injection and Permissions Manifest. 2 were rated high or critical severity. The most severe include Potentially dangerous code pattern detected: base64.*decode and Potentially dangerous code pattern detected: curl.*\|.*sh.

How was fast-io audited?

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

What does a score of 73 mean?

ClawSecure assigned fast-io a security score of 73/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 fast-io

ClawSecure detected 4 security findings in fast-io, spanning Code Injection, Command Injection and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for fast-io

Eliminate dynamic code execution
fast-io 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.
Harden command execution
fast-io 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.
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 SecurityBeyond Static Scans: Why ClawSecure Verifies Agentic IntentUnderstanding Our 3-Layer Audit Protocol

Related AI Agent Security Audits

summarizeScore 85/10025937fcc251c4ccbScore 85/100b2e107e8f7224f2aScore 85/10049d9c51b3ba29229Score 75/10019af8eafb16b72f6Score 75/100

Scanned on April 17, 2026. fast-io 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