← Back to Scanner

tavily Security Audit Report

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

tavily is an AI agent skill, created by bert-builder and published at openclaw/skills. ClawSecure audited tavily across 4 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 80/100 (Safe). The 4 findings concentrate in Malicious Code, Data Exfiltration and Permissions Manifest, including Attempts to access sensitive file: .clawdbot/.env and Environment Variable Enumeration. 1 was rated high or critical severity.

Is tavily safe?

ClawSecure audited tavily and assigned a security score of 80/100 (Safe), identifying 4 findings across Malicious Code and Data Exfiltration. Review the findings below before installing.

What did ClawSecure find in tavily?

ClawSecure identified 4 findings in tavily, concentrated in Malicious Code, Data Exfiltration and Permissions Manifest. 1 was rated high or critical severity. The most severe include Attempts to access sensitive file: .clawdbot/.env and Environment Variable Enumeration.

How was tavily audited?

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

What does a score of 80 mean?

ClawSecure assigned tavily a security score of 80/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 tavily

ClawSecure detected 4 security findings in tavily, spanning Malicious Code, Data Exfiltration, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for tavily

Audit external network connections
tavily connects to external endpoints. Verify every outbound connection goes to a trusted destination. Unauthorized callbacks are a primary indicator of ClawHavoc malware and data exfiltration. ClawSecure's proprietary engine monitors for known malicious endpoints including C2 infrastructure.
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.
Resolve policy violations
tavily trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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 IntentHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

devops-mainScore 75/100TestFilesScore 95/100devops-mainScore 75/100devops-mainScore 75/100redditScore 80/100

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