← Back to Scanner

clawnance Security Audit Report

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

clawnance is an AI agent skill, created by 0xdismissals and published at 0xdismissals/clawnance. ClawSecure audited clawnance across 22 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 2 findings concentrate in Permissions Manifest and Supply Chain, including Vulnerability in axios@1.13.4: Axios is Vulnerable to Denial of Service... and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is clawnance safe?

ClawSecure audited clawnance and assigned a security score of 85/100 (Safe), identifying 2 findings across Permissions Manifest and Supply Chain. Review the findings below before installing.

What did ClawSecure find in clawnance?

ClawSecure identified 2 findings in clawnance, concentrated in Permissions Manifest and Supply Chain. 1 was rated high or critical severity. The most severe include Vulnerability in axios@1.13.4: Axios is Vulnerable to Denial of Service... and Missing config.json - agent may not be properly configured.

How was clawnance audited?

ClawSecure ran clawnance through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 22 files from 0xdismissals/clawnance.

What does a score of 85 mean?

ClawSecure assigned clawnance a security score of 85/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 clawnance

ClawSecure detected 2 security findings in clawnance, spanning Permissions Manifest and Supply Chain.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for clawnance

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
clawnance 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

How to Secure an MCP Server: The 2026 GuideWhat Is MCP Security? Model Context Protocol ExplainedAI Agent Supply Chain Attacks: How Dependencies Become Weapons

Related AI Agent Security Audits

skillsScore 85/100openclaw-skillsScore 85/100wacliScore 95/100falScore 95/100goplacesScore 95/100

Scanned on February 17, 2026. clawnance 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