← Back to Scanner

shipment-tracker Security Audit Report

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

shipment-tracker is an AI agent skill, created by pfrederiksen and published at pfrederiksen/shipment-tracker. ClawSecure audited shipment-tracker 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, Unauthorized Tool Use and Policy Violation, including Skill code uses network libraries but doesn't declare network... and Pattern detected: urllib.request.Request(. None were rated high or critical severity.

Is shipment-tracker safe?

ClawSecure audited shipment-tracker and assigned a security score of 80/100 (Safe), identifying 5 findings across Data Exfiltration and Unauthorized Tool Use. Review the findings below before installing.

What did ClawSecure find in shipment-tracker?

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

How was shipment-tracker audited?

ClawSecure ran shipment-tracker through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 3 files from pfrederiksen/shipment-tracker.

What does a score of 80 mean?

ClawSecure assigned shipment-tracker 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 shipment-tracker

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

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for shipment-tracker

Audit external network connections
shipment-tracker 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
shipment-tracker 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

wacliScore 95/100GitNexusScore 75/100zeroclawScore 85/100antigravity-awesome-skillsScore 75/100kicad-source-mirrorScore 95/100

Scanned on May 2, 2026. shipment-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