← Back to Scanner

earshot Security Audit Report

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

earshot is an AI agent skill, created by Leonxlnx and published at Leonxlnx/earshot. ClawSecure audited earshot across 91 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: Extremely large quantifier range…. None were rated high or critical severity.

Is earshot safe?

ClawSecure audited earshot 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 earshot?

ClawSecure identified 3 findings in earshot, concentrated in ReDoS and Permissions Manifest. The most severe include Missing config.json - agent may not be properly configured and ReDoS vulnerability: Extremely large quantifier range….

How was earshot audited?

ClawSecure ran earshot through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 91 files from Leonxlnx/earshot.

What does a score of 85 mean?

ClawSecure assigned earshot 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 earshot

ClawSecure detected 3 security findings in earshot, spanning ReDoS and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for earshot

Fix ReDoS-prone patterns
earshot 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

aitorScore 95/100wacliScore 95/100uvScore 95/100gstackScore 95/100himalayaScore 85/100

Scanned on October 28, 2026. earshot 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