gno Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

gno is an AI agent skill, created by gmickel and published at openclaw/skills. ClawSecure audited gno across 6 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 78/100 (Medium Risk). The 5 findings concentrate in Command Injection, Policy Violation and Permissions Manifest, 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 gno safe?

ClawSecure audited gno and assigned a security score of 78/100 (Medium Risk), identifying 5 findings across Command Injection and Policy Violation. Review the findings below before installing.

What did ClawSecure find in gno?

ClawSecure identified 5 findings in gno, concentrated in Command Injection, Policy Violation and Permissions Manifest. 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 gno audited?

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

What does a score of 78 mean?

ClawSecure assigned gno a security score of 78/100, placing it in the Medium Risk range. This reflects 5 findings led by Command 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 gno

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

high · Potentially dangerous code pattern detected: curl.*\|.*sh. Code Injection finding detected in README.md.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.
medium · ReDoS vulnerability: Nested quantifiers (potential catastrophic.... ReDoS finding detected in cli-reference.md:633.
low · Pipeline downloads data from the network and executes it: `curl -fsSL.... Command Injection finding detected in README.md:2.
info · Skill manifest does not include a 'license' field. Specifying a license.... Policy Violation finding detected in SKILL.md.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for gno

Harden command execution

gno 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

gno 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.

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.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Understanding Our 3-Layer Audit Protocol→OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→

Related AI Agent Security Audits

ui-ux-pro-max-skillScore 75/100 lossless-clawScore 85/100 GitNexusScore 75/100 MiroFishScore 80/100 antigravity-awesome-skillsScore 75/100

Scanned on April 23, 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