openswarm-fight-club Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

openswarm-fight-club is an AI agent skill, created by 0xmevdad and published at openclaw/skills. ClawSecure audited openswarm-fight-club across 2 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 Code Injection, including Potentially dangerous code pattern detected: base64.*decode and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is openswarm-fight-club safe?

ClawSecure audited openswarm-fight-club and assigned a security score of 85/100 (Safe), identifying 2 findings across Permissions Manifest and Code Injection. Review the findings below before installing.

What did ClawSecure find in openswarm-fight-club?

ClawSecure identified 2 findings in openswarm-fight-club, concentrated in Permissions Manifest and Code Injection. 1 was rated high or critical severity. The most severe include Potentially dangerous code pattern detected: base64.*decode and Missing config.json - agent may not be properly configured.

How was openswarm-fight-club audited?

ClawSecure ran openswarm-fight-club through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 2 files from openclaw/skills.

What does a score of 85 mean?

ClawSecure assigned openswarm-fight-club 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 openswarm-fight-club

ClawSecure detected 2 security findings in openswarm-fight-club, spanning Permissions Manifest and Code Injection.

high · Potentially dangerous code pattern detected: base64.*decode. Code Injection finding detected in skill.md.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for openswarm-fight-club

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

openswarm-fight-club 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.

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 Guide→What Is MCP Security? Model Context Protocol Explained→Why Generic Scanners Fail at AI Agent Security→

Related AI Agent Security Audits

hermes-agentScore 85/100 agent-skillsScore 85/100 agent-creditScore 75/100 Agent-ReachScore 85/100 agent-skillsScore 95/100

Scanned on February 7, 2026. openswarm-fight-club 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