← Back to Scanner

firecrawler Security Audit Report

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

firecrawler is an AI agent skill, created by andrewdmwalker and published at openclaw/skills. ClawSecure audited firecrawler across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 80/100 (Safe). The 5 findings concentrate in Data Exfiltration, Policy Violation and Unauthorized Tool Use, including Pattern detected: import urllib.request and Skill code uses network libraries but doesn't declare network.... None were rated high or critical severity.

Is firecrawler safe?

ClawSecure audited firecrawler and assigned a security score of 80/100 (Safe), identifying 5 findings across Data Exfiltration and Policy Violation. Review the findings below before installing.

What did ClawSecure find in firecrawler?

ClawSecure identified 5 findings in firecrawler, concentrated in Data Exfiltration, Policy Violation and Unauthorized Tool Use. The most severe include Pattern detected: import urllib.request and Skill code uses network libraries but doesn't declare network....

How was firecrawler audited?

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

What does a score of 80 mean?

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

ClawSecure detected 5 security findings in firecrawler, spanning Data Exfiltration, Policy Violation, Unauthorized Tool Use and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for firecrawler

Audit external network connections
firecrawler sends data to external endpoints. Confirm each destination is expected and authorized, and remove any callback that exfiltrates data. ClawSecure monitors for known exfiltration and C2 endpoints.
Resolve policy violations
firecrawler 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

ClawHavoc Explained: The Malware Family Targeting AI AgentsBeyond Static Scans: Why ClawSecure Verifies Agentic IntentOWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards

Related AI Agent Security Audits

browserScore 95/100paperclipScore 80/100summarizeScore 85/100rag-knowledge-engineScore 95/100browserScore 95/100

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