← Back to Scanner

ii-irc Security Audit Report

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

ii-irc is an AI agent skill, created by destructatron and published at openclaw/skills. ClawSecure audited ii-irc across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 90/100 (Safe). The 3 findings concentrate in Policy Violation, Unauthorized Tool Use and Permissions Manifest, including Pattern detected: sudo pacman -S and Missing config.json - agent may not be properly configured. None were rated high or critical severity.

Is ii-irc safe?

ClawSecure audited ii-irc and assigned a security score of 90/100 (Safe), identifying 3 findings across Policy Violation and Unauthorized Tool Use. Review the findings below before installing.

What did ClawSecure find in ii-irc?

ClawSecure identified 3 findings in ii-irc, concentrated in Policy Violation, Unauthorized Tool Use and Permissions Manifest. The most severe include Pattern detected: sudo pacman -S and Missing config.json - agent may not be properly configured.

How was ii-irc audited?

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

What does a score of 90 mean?

ClawSecure assigned ii-irc a security score of 90/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 ii-irc

ClawSecure detected 3 security findings in ii-irc, spanning Policy Violation, Unauthorized Tool Use and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for ii-irc

Resolve policy violations
ii-irc trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security StandardsUnderstanding Our 3-Layer Audit ProtocolHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

kicad-source-mirrorScore 95/100uvScore 95/100awesome-copilotScore 95/100GitNexusScore 75/100crewAIScore 85/100

Scanned on February 7, 2026. ii-irc 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