← Back to Scanner

mamo-cli Security Audit Report

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

mamo-cli is an AI agent skill, created by Moonwell <hello@moonwell.fi> (https://moonwell.fi) and published at openclaw/skills. ClawSecure audited mamo-cli across 35 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 75/100 (Medium Risk). The 3 findings concentrate in Policy Violation, Permissions Manifest and Supply Chain, including Vulnerability in vitest@1.6.0: Vitest allows Remote Code Execution when... and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is mamo-cli safe?

ClawSecure audited mamo-cli and assigned a security score of 75/100 (Medium Risk), identifying 3 findings across Policy Violation and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in mamo-cli?

ClawSecure identified 3 findings in mamo-cli, concentrated in Policy Violation, Permissions Manifest and Supply Chain. 1 was rated high or critical severity. The most severe include Vulnerability in vitest@1.6.0: Vitest allows Remote Code Execution when... and Missing config.json - agent may not be properly configured.

How was mamo-cli audited?

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

What does a score of 75 mean?

ClawSecure assigned mamo-cli a security score of 75/100, placing it in the Medium Risk range. This reflects 3 findings led by Policy Violation 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 mamo-cli

ClawSecure detected 3 security findings in mamo-cli, spanning Policy Violation, Permissions Manifest and Supply Chain.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for mamo-cli

Resolve policy violations
mamo-cli 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.
Update and pin dependencies
mamo-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.
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

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security StandardsUnderstanding Our 3-Layer Audit ProtocolHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

clippyScore 90/100java-concurrency-and-alibaba-standard-auditorScore 85/100java-concurrency-and-alibaba-standard-auditorScore 85/100java-concurrency-and-alibaba-standard-auditorScore 85/100serenity-skillScore 85/100

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