GitNexus Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

GitNexus is an AI agent skill, created by abhigyanpatwari and published at abhigyanpatwari/GitNexus. ClawSecure audited GitNexus across 55 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 75/100 (Moderate). The 3 findings concentrate in Malicious Code, Code Injection and Permissions Manifest, including Attempts to access sensitive file: .ssh/ and Potentially dangerous code pattern detected: curl.*\|.*sh. 2 were rated high or critical severity.

Is GitNexus safe?

ClawSecure audited GitNexus and assigned a security score of 75/100 (Moderate), identifying 3 findings across Malicious Code and Code Injection. Review the findings below before installing.

What did ClawSecure find in GitNexus?

ClawSecure identified 3 findings in GitNexus, concentrated in Malicious Code, Code Injection and Permissions Manifest. 2 were rated high or critical severity. The most severe include Attempts to access sensitive file: .ssh/ and Potentially dangerous code pattern detected: curl.*\|.*sh.

How was GitNexus audited?

ClawSecure ran GitNexus through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 55 files from abhigyanpatwari/GitNexus.

What does a score of 75 mean?

ClawSecure assigned GitNexus a security score of 75/100, placing it in the Moderate range. This reflects 3 findings led by Malicious Code that warrant review before production use. 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 GitNexus

ClawSecure detected 3 security findings in GitNexus, spanning Malicious Code, Code Injection and Permissions Manifest.

high · Attempts to access sensitive file: .ssh/. Malicious Code finding detected in README.md.
high · Potentially dangerous code pattern detected: curl.*\|.*sh. Code Injection finding detected in README.md.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for GitNexus

Audit external network connections

GitNexus connects to external endpoints. Verify every outbound connection goes to a trusted destination. Unauthorized callbacks are a primary indicator of ClawHavoc malware and data exfiltration. ClawSecure's proprietary engine monitors for known malicious endpoints including C2 infrastructure.

Eliminate dynamic code execution

GitNexus evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.

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 Agents→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→Why Generic Scanners Fail at AI Agent Security→

Related AI Agent Security Audits

clawhubScore 85/100 awesome-copilotScore 90/100 awesome-copilotScore 90/100 openclawScore 75/100 crewAIScore 65/100

Scanned on October 18, 2026. GitNexus 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