← Back to Scanner

aitor Security Audit Report

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

aitor is an AI agent skill, created by alien69flow and published at alien69flow/aitor. ClawSecure audited aitor across 130 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 81/100 (Safe). The 8 findings concentrate in Supply Chain and Permissions Manifest, including Vulnerability in vite@5.4.19: vite: `server.fs.deny` bypass… and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is aitor safe?

ClawSecure audited aitor and assigned a security score of 81/100 (Safe), identifying 8 findings across Supply Chain and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in aitor?

ClawSecure identified 8 findings in aitor, concentrated in Supply Chain and Permissions Manifest. 1 was rated high or critical severity. The most severe include Vulnerability in vite@5.4.19: vite: `server.fs.deny` bypass… and Missing config.json - agent may not be properly configured.

How was aitor audited?

ClawSecure ran aitor through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 130 files from alien69flow/aitor.

What does a score of 81 mean?

ClawSecure assigned aitor a security score of 81/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 aitor

ClawSecure detected 8 security findings in aitor, spanning Supply Chain and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for aitor

Update and pin dependencies
aitor depends on packages with supply-chain risk. Pin every dependency to an exact version, update packages with known CVEs to patched releases, and re-audit after each change. ClawSecure checks every dependency against known CVE databases.
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

AI Agent Supply Chain Attacks: How Dependencies Become WeaponsBeyond Static Scans: Why ClawSecure Verifies Agentic Intent

Related AI Agent Security Audits

3f5bb9462d7cb920Score 75/100b4abd97bcb77151aScore 75/100clawdhubScore 75/100mission-controlScore 83/100c1cb277f8f4aa143Score 95/100

Scanned on July 17, 2026. aitor 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