← Back to Scanner

travel-agent Security Audit Report

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

travel-agent is an AI agent skill, created by aszelem and published at openclaw/skills. ClawSecure audited travel-agent across 2 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 95/100 (Safe). The finding concentrates in Permissions Manifest, including Missing config.json - agent may not be properly configured. None were rated high or critical severity.

Is travel-agent safe?

ClawSecure audited travel-agent and assigned a security score of 95/100 (Safe), identifying 1 finding across Permissions Manifest. Review the finding below before installing.

What did ClawSecure find in travel-agent?

ClawSecure identified 1 finding in travel-agent, concentrated in Permissions Manifest. The most severe is Missing config.json - agent may not be properly configured.

How was travel-agent audited?

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

What does a score of 95 mean?

ClawSecure assigned travel-agent a security score of 95/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 1 finding detected is 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 travel-agent

ClawSecure detected 1 security finding in travel-agent, spanning Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for travel-agent

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

How to Secure an MCP Server: The 2026 GuideWhat Is MCP Security? Model Context Protocol ExplainedBest AI Agent Security Tools in 2026: How to Choose

Related AI Agent Security Audits

04_AI_AGENTENScore 95/10004_AI_AGENTENScore 95/100.agentScore 95/100.agentScore 95/100.agentScore 95/100

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