command-center Security Audit Report
command-center is an AI agent skill, created by OpenClaw Contributors. ClawSecure audited command-center across 81 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 0/100 (High Risk). The 65 findings concentrate in Data Exfiltration, Command Injection and Malicious Code, including Suspicious Pattern: require("child_process") and Suspicious Pattern: require("child_process"). 55 were rated high or critical severity.
Is command-center safe?
ClawSecure audited command-center and assigned a security score of 0/100 (High Risk), identifying 65 findings across Data Exfiltration and Command Injection. Review the findings below before installing.
What did ClawSecure find in command-center?
ClawSecure identified 65 findings in command-center, concentrated in Data Exfiltration, Command Injection and Malicious Code. 55 were rated high or critical severity. The most severe include Suspicious Pattern: require("child_process") and Suspicious Pattern: require("child_process").
How was command-center audited?
ClawSecure ran command-center through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 81 files.
What does a score of 0 mean?
ClawSecure assigned command-center a security score of 0/100, placing it in the High Risk range. This is driven by 65 findings led by Data Exfiltration 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 command-center
ClawSecure detected 65 security findings in command-center, spanning Data Exfiltration, Command Injection, Malicious Code and Policy Violation.
- critical · Suspicious Pattern: require("child_process"). Command Injection finding detected in
lib/server.js:10. - critical · Suspicious Pattern: require("child_process"). Command Injection finding detected in
lib/server.js:436. - critical · Suspicious Pattern: require("child_process"). Command Injection finding detected in
lib/server.js:2446. - critical · Suspicious Pattern: require("child_process"). Command Injection finding detected in
lib/server.js:2624. - critical · Suspicious Pattern: require("child_process"). Command Injection finding detected in
lib/server.js:2821. - critical · Suspicious Pattern: require("child_process"). Command Injection finding detected in
scripts/linear-sync.js:492. - critical · Suspicious Pattern: execSync(. Command Injection finding detected in
scripts/linear-sync.js:495. - critical · Suspicious Pattern: require("child_process"). Command Injection finding detected in
src/llm-usage.js:3. - critical · Suspicious Pattern: require("child_process"). Command Injection finding detected in
src/llm-usage.js:220. - critical · Suspicious Pattern: require("child_process"). Command Injection finding detected in
src/openclaw.js:5. - critical · Suspicious Pattern: require("child_process"). Command Injection finding detected in
src/state.js:4. - critical · Suspicious Pattern: require("child_process"). Command Injection finding detected in
src/utils.js:5.
Showing the 12 highest-severity of 65 findings. The full interactive list appears below.
3-Layer Audit Protocol
Security Recommendations for command-center
Audit external network connections
Harden command execution
Resolve policy violations
Related Security Research
ClawHavoc Explained: The Malware Family Targeting AI Agents→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→Related AI Agent Security Audits
Scanned on March 27, 2026. command-center is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.