← Back to Scanner

cron-creator Security Audit Report

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

cron-creator is an AI agent skill, created by digitaladaption and published at digitaladaption/cron-creator. ClawSecure audited cron-creator across 4 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 35/100 (High Risk). The 5 findings concentrate in Cve, Policy Violation and Permissions Manifest, including CVE-2026-25253: Dangerous configuration modification detected... and CVE-2026-25253: Dangerous configuration modification detected.... 3 were rated high or critical severity.

Is cron-creator safe?

ClawSecure audited cron-creator and assigned a security score of 35/100 (High Risk), identifying 5 findings across Cve and Policy Violation. Review the findings below before installing.

What did ClawSecure find in cron-creator?

ClawSecure identified 5 findings in cron-creator, concentrated in Cve, Policy Violation and Permissions Manifest. 3 were rated high or critical severity. The most severe include CVE-2026-25253: Dangerous configuration modification detected... and CVE-2026-25253: Dangerous configuration modification detected....

How was cron-creator audited?

ClawSecure ran cron-creator through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 4 files from digitaladaption/cron-creator.

What does a score of 35 mean?

ClawSecure assigned cron-creator a security score of 35/100, placing it in the High Risk range. This is driven by 5 findings led by Cve that should be addressed before 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 cron-creator

ClawSecure detected 5 security findings in cron-creator, spanning Cve, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for cron-creator

Resolve policy violations
cron-creator 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

mission-controlScore 38/100self-improving-agent-3Score 30/100@openclaw/dashboardScore 45/100claw-controlScore 25/100agent-councilScore 50/100

Scanned on February 18, 2026. cron-creator 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