← Back to Scanner

openclast-wallet Security Audit Report

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

openclast-wallet is an AI agent skill, created by fabriziogianni7 and published at fabriziogianni7/openclast-wallet. ClawSecure audited openclast-wallet across 34 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 0/100 (High Risk). The 460 findings concentrate in Supply Chain and Permissions Manifest, including Vulnerability in openclaw@2026.2.1: OpenClaw: Pairing-scoped device... and Vulnerability in openclaw@2026.2.1: OpenClaw has an inbound allowlist.... 180 were rated high or critical severity.

Is openclast-wallet safe?

ClawSecure audited openclast-wallet and assigned a security score of 0/100 (High Risk), identifying 460 findings across Supply Chain and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in openclast-wallet?

ClawSecure identified 460 findings in openclast-wallet, concentrated in Supply Chain and Permissions Manifest. 180 were rated high or critical severity. The most severe include Vulnerability in openclaw@2026.2.1: OpenClaw: Pairing-scoped device... and Vulnerability in openclaw@2026.2.1: OpenClaw has an inbound allowlist....

How was openclast-wallet audited?

ClawSecure ran openclast-wallet through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 34 files from fabriziogianni7/openclast-wallet.

What does a score of 0 mean?

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

ClawSecure detected 460 security findings in openclast-wallet, spanning Supply Chain and Permissions Manifest.

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

3-Layer Audit Protocol

Security Recommendations for openclast-wallet

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

Related AI Agent Security Audits

awesome-openclaw-skillsScore 0/100memUScore 0/100understand-anythingScore 0/10062ac696296b54aadScore 0/1006bc837afc1a86e89Score 0/100

Scanned on May 3, 2026. openclast-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