← Back to Scanner

llm-wallet Security Audit Report

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

llm-wallet is an AI agent skill, created by akshatgada and published at akshatgada/llm-wallet. ClawSecure audited llm-wallet across 26 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 53/100 (Medium Risk). The 5 findings concentrate in Supply Chain and Permissions Manifest, including Vulnerability in vitest@2.0.0: Vitest allows Remote Code Execution when... and Vulnerability in @modelcontextprotocol/sdk@1.9.0: Anthropic's MCP.... 3 were rated high or critical severity.

Is llm-wallet safe?

ClawSecure audited llm-wallet and assigned a security score of 53/100 (Medium Risk), identifying 5 findings across Supply Chain and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in llm-wallet?

ClawSecure identified 5 findings in llm-wallet, concentrated in Supply Chain and Permissions Manifest. 3 were rated high or critical severity. The most severe include Vulnerability in vitest@2.0.0: Vitest allows Remote Code Execution when... and Vulnerability in @modelcontextprotocol/sdk@1.9.0: Anthropic's MCP....

How was llm-wallet audited?

ClawSecure ran llm-wallet through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 26 files from akshatgada/llm-wallet.

What does a score of 53 mean?

ClawSecure assigned llm-wallet a security score of 53/100, placing it in the Medium Risk range. This reflects 5 findings led by Supply Chain that warrant review before production 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 llm-wallet

ClawSecure detected 5 security findings in llm-wallet, spanning Supply Chain and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for llm-wallet

Update and pin dependencies
llm-wallet 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

openclawScore 55/100gnoScore 45/100aitorScore 61/100keepScore 45/100Amazon-SkillsScore 55/100

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