← Back to Scanner

google-chat Security Audit Report

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

google-chat is an AI agent skill, created by darconada and published at openclaw/skills. ClawSecure audited google-chat across 6 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 Policy Violation, Data Exfiltration and Unauthorized Tool Use, including Pattern detected: import urllib.request and Skill code uses network libraries but doesn't declare network.... None were rated high or critical severity.

Is google-chat safe?

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

What did ClawSecure find in google-chat?

ClawSecure identified 4 findings in google-chat, concentrated in Policy Violation, Data Exfiltration and Unauthorized Tool Use. The most severe include Pattern detected: import urllib.request and Skill code uses network libraries but doesn't declare network....

How was google-chat audited?

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

What does a score of 85 mean?

ClawSecure assigned google-chat 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 google-chat

ClawSecure detected 4 security findings in google-chat, spanning Policy Violation, Data Exfiltration, Unauthorized Tool Use and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for google-chat

Resolve policy violations
google-chat trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Audit external network connections
google-chat 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.
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

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security StandardsUnderstanding Our 3-Layer Audit ProtocolClawHavoc Explained: The Malware Family Targeting AI Agents

Related AI Agent Security Audits

summarizeScore 85/100summarizeScore 85/100academic-glowup (1)Score 95/100sdicsc-fund-query-compareScore 73/100pdfScore 95/100

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