← Back to Scanner

@rickybloomfield/ouraclaw Security Audit Report

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

@rickybloomfield/ouraclaw is an AI agent skill, created by Ricky Bloomfield and published at rickybloomfield/OuraClaw. ClawSecure audited @rickybloomfield/ouraclaw across 17 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 80/100 (Safe). The 3 findings concentrate in Permissions Manifest, Code Injection and ReDoS, including Potentially dangerous code pattern detected: exec\( and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is @rickybloomfield/ouraclaw safe?

ClawSecure audited @rickybloomfield/ouraclaw and assigned a security score of 80/100 (Safe), identifying 3 findings across Permissions Manifest and Code Injection. Review the findings below before installing.

What did ClawSecure find in @rickybloomfield/ouraclaw?

ClawSecure identified 3 findings in @rickybloomfield/ouraclaw, concentrated in Permissions Manifest, Code Injection and ReDoS. 1 was rated high or critical severity. The most severe include Potentially dangerous code pattern detected: exec\( and Missing config.json - agent may not be properly configured.

How was @rickybloomfield/ouraclaw audited?

ClawSecure ran @rickybloomfield/ouraclaw through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 17 files from rickybloomfield/OuraClaw.

What does a score of 80 mean?

ClawSecure assigned @rickybloomfield/ouraclaw a security score of 80/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 @rickybloomfield/ouraclaw

ClawSecure detected 3 security findings in @rickybloomfield/ouraclaw, spanning Permissions Manifest, Code Injection and ReDoS.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for @rickybloomfield/ouraclaw

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
@rickybloomfield/ouraclaw 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
@rickybloomfield/ouraclaw 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.
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

How to Secure an MCP Server: The 2026 GuideWhat Is MCP Security? Model Context Protocol ExplainedWhy Generic Scanners Fail at AI Agent Security

Related AI Agent Security Audits

clawdhubScore 75/100b4abd97bcb77151aScore 75/100mission-controlScore 83/100c1cb277f8f4aa143Score 95/10019af8eafb16b72f6Score 75/100

Scanned on April 17, 2026. @rickybloomfield/ouraclaw 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