← Back to Scanner

oh-my-claudecode Security Audit Report

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

oh-my-claudecode is an AI agent skill, created by Yeachan-Heo and published at Yeachan-Heo/oh-my-claudecode. ClawSecure audited oh-my-claudecode across 50 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 3 findings concentrate in ReDoS and Permissions Manifest, including Missing config.json - agent may not be properly configured and ReDoS vulnerability: Nested quantifiers (potential…. None were rated high or critical severity.

Is oh-my-claudecode safe?

ClawSecure audited oh-my-claudecode and assigned a security score of 85/100 (Safe), identifying 3 findings across ReDoS and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in oh-my-claudecode?

ClawSecure identified 3 findings in oh-my-claudecode, concentrated in ReDoS and Permissions Manifest. The most severe include Missing config.json - agent may not be properly configured and ReDoS vulnerability: Nested quantifiers (potential….

How was oh-my-claudecode audited?

ClawSecure ran oh-my-claudecode through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 50 files from Yeachan-Heo/oh-my-claudecode.

What does a score of 85 mean?

ClawSecure assigned oh-my-claudecode a security score of 85/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 3 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 oh-my-claudecode

ClawSecure detected 3 security findings in oh-my-claudecode, spanning ReDoS and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for oh-my-claudecode

Fix ReDoS-prone patterns
oh-my-claudecode 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.
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

@martian-engineering/lossless-clawScore 85/100@penpot/mcpScore 85/100everything-claude-codeScore 80/100claude-code-templatesScore 85/100@modelcontextprotocol/serversScore 90/100

Scanned on November 11, 2026. oh-my-claudecode 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