historical-cpu-spikes Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

historical-cpu-spikes is an AI agent skill. ClawSecure audited historical-cpu-spikes across 1 file through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 95/100 (Safe). The 2 findings concentrate in Permissions Manifest and Policy Violation, including Missing config.json - agent may not be properly configured and Missing License Declaration. None were rated high or critical severity.

Is historical-cpu-spikes safe?

ClawSecure audited historical-cpu-spikes and assigned a security score of 95/100 (Safe), identifying 2 findings across Permissions Manifest and Policy Violation. Review the findings below before installing.

What did ClawSecure find in historical-cpu-spikes?

ClawSecure identified 2 findings in historical-cpu-spikes, concentrated in Permissions Manifest and Policy Violation. The most severe include Missing config.json - agent may not be properly configured and Missing License Declaration.

How was historical-cpu-spikes audited?

ClawSecure ran historical-cpu-spikes through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 1 file.

What does a score of 95 mean?

ClawSecure assigned historical-cpu-spikes a security score of 95/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 historical-cpu-spikes

ClawSecure detected 2 security findings in historical-cpu-spikes, spanning Permissions Manifest and Policy Violation.

medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.
info · Missing License Declaration. Policy Violation finding detected in SKILL.md.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for historical-cpu-spikes

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.

Resolve policy violations

historical-cpu-spikes trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.

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 Guide→What Is MCP Security? Model Context Protocol Explained→OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards→

Related AI Agent Security Audits

ai-daily-briefingScore 85/100 summarizeScore 85/100 browserScore 95/100 paperclipScore 80/100 rag-knowledge-engineScore 95/100

Scanned on April 5, 2026. historical-cpu-spikes 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