← Back to Scanner

gsc Security Audit Report

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

gsc is an AI agent skill, created by jdrhyne and published at openclaw/skills. ClawSecure audited gsc across 4 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 4 findings concentrate in Data Exfiltration, Policy Violation and Permissions Manifest, including Script iterates through environment variables in... and Script iterates through environment variables in.... None were rated high or critical severity.

Is gsc safe?

ClawSecure audited gsc and assigned a security score of 85/100 (Safe), identifying 4 findings across Data Exfiltration and Policy Violation. Review the findings below before installing.

What did ClawSecure find in gsc?

ClawSecure identified 4 findings in gsc, concentrated in Data Exfiltration, Policy Violation and Permissions Manifest. The most severe include Script iterates through environment variables in... and Script iterates through environment variables in....

How was gsc audited?

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

What does a score of 85 mean?

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

ClawSecure detected 4 security findings in gsc, spanning Data Exfiltration, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for gsc

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

c1cb277f8f4aa143Score 95/10019af8eafb16b72f6Score 75/100b4abd97bcb77151aScore 75/10030bdbb41c9aa6d07Score 95/100624aee5f17bf59b1Score 95/100

Scanned on March 2, 2026. gsc 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