← Back to Scanner

ga4-analytics Security Audit Report

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

ga4-analytics is an AI agent skill, created by adamkristopher and published at openclaw/skills. ClawSecure audited ga4-analytics across 17 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 55/100 (Medium Risk). The 4 findings concentrate in Hardcoded Secrets, Policy Violation and Permissions Manifest, including Pattern detected: -----BEGIN PRIVATE KEY----- and Detects potential exposure of sensitive information like API keys,.... 2 were rated high or critical severity.

Is ga4-analytics safe?

ClawSecure audited ga4-analytics and assigned a security score of 55/100 (Medium Risk), identifying 4 findings across Hardcoded Secrets and Policy Violation. Review the findings below before installing.

What did ClawSecure find in ga4-analytics?

ClawSecure identified 4 findings in ga4-analytics, concentrated in Hardcoded Secrets, Policy Violation and Permissions Manifest. 2 were rated high or critical severity. The most severe include Pattern detected: -----BEGIN PRIVATE KEY----- and Detects potential exposure of sensitive information like API keys,....

How was ga4-analytics audited?

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

What does a score of 55 mean?

ClawSecure assigned ga4-analytics a security score of 55/100, placing it in the Medium Risk range. This reflects 4 findings led by Hardcoded Secrets 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 ga4-analytics

ClawSecure detected 4 security findings in ga4-analytics, spanning Hardcoded Secrets, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for ga4-analytics

Resolve policy violations
ga4-analytics 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

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security StandardsUnderstanding Our 3-Layer Audit ProtocolHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

probe-14-webhookScore 50/100whatsapp-ultimateScore 70/100zoho-email-integrationScore 65/100clawdbot-zoho-emailScore 65/100clawdbot-zoho-emailScore 65/100

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