← Back to Scanner

llm-wiki Security Audit Report

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

llm-wiki is an AI agent skill. ClawSecure audited llm-wiki across 14 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 Data Exfiltration, Permissions Manifest and Policy Violation, including Environment Variable Enumeration and Missing config.json - agent may not be properly configured. None were rated high or critical severity.

Is llm-wiki safe?

ClawSecure audited llm-wiki and assigned a security score of 90/100 (Safe), identifying 3 findings across Data Exfiltration and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in llm-wiki?

ClawSecure identified 3 findings in llm-wiki, concentrated in Data Exfiltration, Permissions Manifest and Policy Violation. The most severe include Environment Variable Enumeration and Missing config.json - agent may not be properly configured.

How was llm-wiki audited?

ClawSecure ran llm-wiki through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 14 files.

What does a score of 90 mean?

ClawSecure assigned llm-wiki 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 llm-wiki

ClawSecure detected 3 security findings in llm-wiki, spanning Data Exfiltration, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for llm-wiki

Audit external network connections
llm-wiki sends data to external endpoints. Confirm each destination is expected and authorized, and remove any callback that exfiltrates data. ClawSecure monitors for known exfiltration and C2 endpoints.
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.
Resolve policy violations
llm-wiki trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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

ClawHavoc Explained: The Malware Family Targeting AI AgentsBeyond Static Scans: Why ClawSecure Verifies Agentic IntentHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

songseeScore 95/100goplacesScore 95/100gogcliScore 95/100ui-ux-pro-max-skillScore 75/100clawdhubScore 75/100

Scanned on June 12, 2026. llm-wiki 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