← Back to Scanner

browser-cash Security Audit Report

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

browser-cash is an AI agent skill, created by alexander-spring and published at openclaw/skills. ClawSecure audited browser-cash across 2 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 4 findings concentrate in Command Injection, Policy Violation and Permissions Manifest, including Detects dangerous code execution patterns with untrusted input in agent... and Detects dangerous code execution patterns with untrusted input in agent.... None were rated high or critical severity.

Is browser-cash safe?

ClawSecure audited browser-cash and assigned a security score of 85/100 (Safe), identifying 4 findings across Command Injection and Policy Violation. Review the findings below before installing.

What did ClawSecure find in browser-cash?

ClawSecure identified 4 findings in browser-cash, concentrated in Command Injection, Policy Violation and Permissions Manifest. The most severe include Detects dangerous code execution patterns with untrusted input in agent... and Detects dangerous code execution patterns with untrusted input in agent....

How was browser-cash audited?

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

What does a score of 85 mean?

ClawSecure assigned browser-cash a security score of 85/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 4 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 browser-cash

ClawSecure detected 4 security findings in browser-cash, spanning Command Injection, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for browser-cash

Harden command execution
browser-cash constructs or runs system commands. Validate that commands are built only from trusted inputs, never pass user-controlled strings directly to a shell, and restrict execution to an allow-list of expected commands.
Resolve policy violations
browser-cash trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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

Why Generic Scanners Fail at AI Agent Security→Understanding Our 3-Layer Audit Protocol→OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→

Related AI Agent Security Audits

summarizeScore 85/100summarizeScore 85/100summarizeScore 85/100summarizeScore 85/100summarizeScore 85/100

Scanned on February 7, 2026. browser-cash 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