← Back to Scanner

gitclassic Security Audit Report

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

gitclassic is an AI agent skill, created by heythisischris and published at openclaw/skills. ClawSecure audited gitclassic across 2 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 90/100 (Safe). The 2 findings concentrate in Skill Discovery Abuse and Permissions Manifest, including Detects protocol manipulation via capability inflation in skill... and Missing config.json - agent may not be properly configured. None were rated high or critical severity.

Is gitclassic safe?

ClawSecure audited gitclassic and assigned a security score of 90/100 (Safe), identifying 2 findings across Skill Discovery Abuse and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in gitclassic?

ClawSecure identified 2 findings in gitclassic, concentrated in Skill Discovery Abuse and Permissions Manifest. The most severe include Detects protocol manipulation via capability inflation in skill... and Missing config.json - agent may not be properly configured.

How was gitclassic audited?

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

What does a score of 90 mean?

ClawSecure assigned gitclassic a security score of 90/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 gitclassic

ClawSecure detected 2 security findings in gitclassic, spanning Skill Discovery Abuse and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for gitclassic

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

skillsScore 85/100openclaw-skillsScore 85/100wacliScore 95/100falScore 95/100goplacesScore 95/100

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