← Back to Scanner

pollinations Security Audit Report

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

pollinations is an AI agent skill, created by isaacgounton and published at openclaw/skills. ClawSecure audited pollinations across 10 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 3 findings concentrate in Policy Violation, Permissions Manifest and Code Injection, including Potentially dangerous code pattern detected: base64.*decode and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is pollinations safe?

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

What did ClawSecure find in pollinations?

ClawSecure identified 3 findings in pollinations, concentrated in Policy Violation, Permissions Manifest and Code Injection. 1 was rated high or critical severity. The most severe include Potentially dangerous code pattern detected: base64.*decode and Missing config.json - agent may not be properly configured.

How was pollinations audited?

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

What does a score of 85 mean?

ClawSecure assigned pollinations a security score of 85/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status, though 1 finding was rated high or critical and warrants review. 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 pollinations

ClawSecure detected 3 security findings in pollinations, spanning Policy Violation, Permissions Manifest and Code Injection.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for pollinations

Resolve policy violations
pollinations 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.
Eliminate dynamic code execution
pollinations evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.
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

Agent-ReachScore 75/100wake-upScore 95/100agent-creditScore 75/10004_AI_AGENTENScore 95/10004_AI_AGENTENScore 95/100

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