← Back to Scanner

gno Security Audit Report

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

gno is an AI agent skill, created by gmickel and published at gmickel/gno. ClawSecure audited gno across 50 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 45/100 (High Risk). The 7 findings concentrate in Code Injection, ReDoS and Permissions Manifest, including Potentially dangerous code pattern detected: curl.*\|.*sh and Potentially dangerous code pattern detected: eval\(. 4 were rated high or critical severity.

Is gno safe?

ClawSecure audited gno and assigned a security score of 45/100 (High Risk), identifying 7 findings across Code Injection and ReDoS. Review the findings below before installing.

What did ClawSecure find in gno?

ClawSecure identified 7 findings in gno, concentrated in Code Injection, ReDoS and Permissions Manifest. 4 were rated high or critical severity. The most severe include Potentially dangerous code pattern detected: curl.*\|.*sh and Potentially dangerous code pattern detected: eval\(.

How was gno audited?

ClawSecure ran gno through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 50 files from gmickel/gno.

What does a score of 45 mean?

ClawSecure assigned gno a security score of 45/100, placing it in the High Risk range. This is driven by 7 findings led by Code Injection that should be addressed before 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 gno

ClawSecure detected 7 security findings in gno, spanning Code Injection, ReDoS and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for gno

Eliminate dynamic code execution
gno 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.
Fix ReDoS-prone patterns
gno contains regular expressions vulnerable to catastrophic backtracking (ReDoS). Replace vulnerable patterns, bound input length, and prefer linear-time matching so a crafted input cannot hang the agent.
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.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→

Related AI Agent Security Audits

openclawScore 55/100claude-memScore 35/100keepScore 45/100open-webuiScore 35/100Amazon-SkillsScore 55/100

Scanned on August 5, 2026. gno 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