← Back to Scanner

whatsmolt Security Audit Report

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

whatsmolt is an AI agent skill, created by Goudan and published at crypticdriver/whatsmolt. ClawSecure audited whatsmolt across 50 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 11/100 (High Risk). The 17 findings concentrate in Supply Chain and Permissions Manifest, including Vulnerability in next@15.1.3: Next.js is vulnerable to RCE in React... and Vulnerability in next@15.1.3: Authorization Bypass in Next.js Middleware. 6 were rated high or critical severity.

Is whatsmolt safe?

ClawSecure audited whatsmolt and assigned a security score of 11/100 (High Risk), identifying 17 findings across Supply Chain and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in whatsmolt?

ClawSecure identified 17 findings in whatsmolt, concentrated in Supply Chain and Permissions Manifest. 6 were rated high or critical severity. The most severe include Vulnerability in next@15.1.3: Next.js is vulnerable to RCE in React... and Vulnerability in next@15.1.3: Authorization Bypass in Next.js Middleware.

How was whatsmolt audited?

ClawSecure ran whatsmolt through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 50 files from crypticdriver/whatsmolt.

What does a score of 11 mean?

ClawSecure assigned whatsmolt a security score of 11/100, placing it in the High Risk range. This is driven by 17 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 whatsmolt

ClawSecure detected 17 security findings in whatsmolt, spanning Supply Chain and Permissions Manifest.

Showing the 12 highest-severity of 17 findings. The full interactive list appears below.

3-Layer Audit Protocol

Security Recommendations for whatsmolt

Update and pin dependencies
whatsmolt 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 Intent

Related AI Agent Security Audits

memUScore 0/100fzfScore 25/100understand-anythingScore 0/10062ac696296b54aadScore 0/1006bc837afc1a86e89Score 0/100

Scanned on May 2, 2026. whatsmolt 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