← Back to Scanner

vehicle-tracker Security Audit Report

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

vehicle-tracker is an AI agent skill, created by huchengtw and published at openclaw/skills. ClawSecure audited vehicle-tracker across 7 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 98/100 (Safe). The 2 findings concentrate in Policy Violation and Verification, including No GitHub source URL - cannot verify agent origin and Skill manifest does not include a 'license' field. Specifying a license.... None were rated high or critical severity.

Is vehicle-tracker safe?

ClawSecure audited vehicle-tracker and assigned a security score of 98/100 (Safe), identifying 2 findings across Policy Violation and Verification. Review the findings below before installing.

What did ClawSecure find in vehicle-tracker?

ClawSecure identified 2 findings in vehicle-tracker, concentrated in Policy Violation and Verification. The most severe include No GitHub source URL - cannot verify agent origin and Skill manifest does not include a 'license' field. Specifying a license....

How was vehicle-tracker audited?

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

What does a score of 98 mean?

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

ClawSecure detected 2 security findings in vehicle-tracker, spanning Policy Violation and Verification.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for vehicle-tracker

Resolve policy violations
vehicle-tracker 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.
Add a config.json permissions manifest
A config.json file declares what permissions an agent component needs: file system access, network requests, shell execution and more. Without it, users have no visibility into what the component can do before installing. Adding a permissions manifest is the single most impactful security improvement for any AI agent skill.

Related Security Research

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→Understanding Our 3-Layer Audit Protocol→Best AI Agent Security Tools in 2026: How to Choose→

Related AI Agent Security Audits

JIRA-Assistant-SkillsScore 95/100thingsboard-skillScore 85/100jira-bug-queryScore 90/100wordpress-proScore 95/100File_managerScore 98/100

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