← Back to Scanner

clawdgigs Security Audit Report

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

clawdgigs is an AI agent skill, created by Bennie The Dev and published at benniethedev/clawdgigs. ClawSecure audited clawdgigs across 48 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 83/100 (Safe). The 7 findings concentrate in Supply Chain and Permissions Manifest, including Vulnerability in next@16.1.6: Next.js has a Denial of Service with... and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is clawdgigs safe?

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

What did ClawSecure find in clawdgigs?

ClawSecure identified 7 findings in clawdgigs, concentrated in Supply Chain and Permissions Manifest. 1 was rated high or critical severity. The most severe include Vulnerability in next@16.1.6: Next.js has a Denial of Service with... and Missing config.json - agent may not be properly configured.

How was clawdgigs audited?

ClawSecure ran clawdgigs through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 48 files from benniethedev/clawdgigs.

What does a score of 83 mean?

ClawSecure assigned clawdgigs a security score of 83/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 clawdgigs

ClawSecure detected 7 security findings in clawdgigs, spanning Supply Chain and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for clawdgigs

Update and pin dependencies
clawdgigs 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

MiroFishScore 80/100ui-ux-pro-max-skillScore 75/100uvScore 95/100antigravity-awesome-skillsScore 75/100ClawSecScore 95/100

Scanned on May 5, 2026. clawdgigs 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