← Back to Scanner

wikijs-cli Security Audit Report

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

wikijs-cli is an AI agent skill, created by OpenClaw and published at openclaw/skills. ClawSecure audited wikijs-cli across 14 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 45/100 (High Risk). The 5 findings concentrate in Supply Chain and Permissions Manifest, including Vulnerability in form-data@4.0.0: form-data uses unsafe random function... and Vulnerability in axios@1.6.0: Axios is vulnerable to DoS attack through.... 4 were rated high or critical severity.

Is wikijs-cli safe?

ClawSecure audited wikijs-cli and assigned a security score of 45/100 (High Risk), identifying 5 findings across Supply Chain and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in wikijs-cli?

ClawSecure identified 5 findings in wikijs-cli, concentrated in Supply Chain and Permissions Manifest. 4 were rated high or critical severity. The most severe include Vulnerability in form-data@4.0.0: form-data uses unsafe random function... and Vulnerability in axios@1.6.0: Axios is vulnerable to DoS attack through....

How was wikijs-cli audited?

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

What does a score of 45 mean?

ClawSecure assigned wikijs-cli a security score of 45/100, placing it in the High Risk range. This is driven by 5 findings led by Supply Chain that should be addressed before use. 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 wikijs-cli

ClawSecure detected 5 security findings in wikijs-cli, spanning Supply Chain and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for wikijs-cli

Update and pin dependencies
wikijs-cli 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.
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

AI Agent Supply Chain Attacks: How Dependencies Become WeaponsBeyond Static Scans: Why ClawSecure Verifies Agentic IntentHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

@modelcontextprotocol/serversScore 50/100gitlab-cli-skillsScore 55/100c4-nexus-react-ecommerce-assignmentScore 31/100nginx-analyzeScore 60/100nginx-analyzeScore 60/100

Scanned on February 7, 2026. wikijs-cli 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