← Back to Scanner

nano-mailer Security Audit Report

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

nano-mailer is an AI agent skill. ClawSecure audited nano-mailer across 7 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 93/100 (Safe). The 3 findings concentrate in Policy Violation and Permissions Manifest, including Missing config.json - agent may not be properly configured and __pycache__ directory found at scripts/__pycache__/…. None were rated high or critical severity.

Is nano-mailer safe?

ClawSecure audited nano-mailer and assigned a security score of 93/100 (Safe), identifying 3 findings across Policy Violation and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in nano-mailer?

ClawSecure identified 3 findings in nano-mailer, concentrated in Policy Violation and Permissions Manifest. The most severe include Missing config.json - agent may not be properly configured and __pycache__ directory found at scripts/__pycache__/….

How was nano-mailer audited?

ClawSecure ran nano-mailer through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 7 files.

What does a score of 93 mean?

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

ClawSecure detected 3 security findings in nano-mailer, spanning Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for nano-mailer

Resolve policy violations
nano-mailer 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

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

TestFilesScore 95/100redditScore 80/100deep-research-proScore 85/100gogScore 95/100sql-toolkitScore 95/100

Scanned on March 3, 2026. nano-mailer 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