← Back to Scanner

@betrue/openclaw-claude-code-plugin Security Audit Report

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

@betrue/openclaw-claude-code-plugin is an AI agent skill, created by Betrue <hello@betrue.fr> and published at alizarion/openclaw-claude-code-plugin. ClawSecure audited @betrue/openclaw-claude-code-plugin across 36 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 4 findings concentrate in ReDoS, Permissions Manifest and Supply Chain, including Missing config.json - agent may not be properly configured and ReDoS vulnerability: Nested quantifiers (potential…. None were rated high or critical severity.

Is @betrue/openclaw-claude-code-plugin safe?

ClawSecure audited @betrue/openclaw-claude-code-plugin and assigned a security score of 85/100 (Safe), identifying 4 findings across ReDoS and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in @betrue/openclaw-claude-code-plugin?

ClawSecure identified 4 findings in @betrue/openclaw-claude-code-plugin, concentrated in ReDoS, Permissions Manifest and Supply Chain. The most severe include Missing config.json - agent may not be properly configured and ReDoS vulnerability: Nested quantifiers (potential….

How was @betrue/openclaw-claude-code-plugin audited?

ClawSecure ran @betrue/openclaw-claude-code-plugin through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 36 files from alizarion/openclaw-claude-code-plugin.

What does a score of 85 mean?

ClawSecure assigned @betrue/openclaw-claude-code-plugin a security score of 85/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 4 findings detected are lower-severity. 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 @betrue/openclaw-claude-code-plugin

ClawSecure detected 4 security findings in @betrue/openclaw-claude-code-plugin, spanning ReDoS, Permissions Manifest and Supply Chain.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for @betrue/openclaw-claude-code-plugin

Fix ReDoS-prone patterns
@betrue/openclaw-claude-code-plugin 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.
Update and pin dependencies
@betrue/openclaw-claude-code-plugin depends on packages with supply-chain risk. Pin every dependency to an exact version, update packages with known CVEs to patched releases, and re-audit after each change. ClawSecure checks every dependency against known CVE databases.
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→Understanding Our 3-Layer Audit Protocol→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

devops-mainScore 75/100TestFilesScore 95/100devops-mainScore 75/100devops-mainScore 75/100redditScore 80/100

Scanned on March 2, 2026. @betrue/openclaw-claude-code-plugin 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