Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Audit and harden OpenClaw configuration for security. Scans openclaw.json for vulnerabilities, exposed credentials, insecure gateway settings, overly permiss...
Audit and harden OpenClaw configuration for security. Scans openclaw.json for vulnerabilities, exposed credentials, insecure gateway settings, overly permiss...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Audit your OpenClaw configuration and apply security best practices automatically.
# Full security audit (read-only, no changes) python scripts/hardener.py audit # Audit a specific config file python scripts/hardener.py audit --config /path/to/openclaw.json # Audit with JSON output python scripts/hardener.py audit -f json # Auto-fix issues (creates backup first) python scripts/hardener.py fix # Fix specific issues only python scripts/hardener.py fix --only gateway,permissions # Scan for exposed credentials in config python scripts/hardener.py scan-secrets # Generate a security report python scripts/hardener.py report -o security-report.md # Check file permissions python scripts/hardener.py check-perms
CommandArgsDescriptionaudit[--config PATH] [-f FORMAT]Full security audit (read-only)fix[--config PATH] [--only CHECKS]Auto-fix issues (with backup)scan-secrets[--config PATH]Scan for exposed API keys/tokensreport[-o FILE]Generate detailed security reportcheck-perms[--config-dir PATH]Check file permissions
CheckSeverityDescriptiongateway-bindCRITICALGateway not bound to loopbackexposed-keysCRITICALAPI keys in config instead of .envinsecure-authHIGHallowInsecureAuth or dangerouslyDisableDeviceAuth enabledexec-sandboxHIGHexec sandbox mode not set to restrictedfile-permsHIGHConfig files readable by others (not 600)agent-allow-allMEDIUMagentToAgent.allow: ["*"] is overly permissiveno-heartbeatMEDIUMNo heartbeat configured (can't detect outages)no-session-resetMEDIUMNo session reset policy (memory leak risk)no-pruningLOWNo context pruning (cost and performance impact)no-memory-flushLOWMemory flush disabled (context loss on pruning)
The audit produces a security score from 0-100: 90-100: Excellent โ production-ready 70-89: Good โ minor improvements recommended 50-69: Fair โ several issues to address 0-49: Poor โ critical issues require immediate attention
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ OPENCLAW SECURITY AUDIT โ โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฃ โ Score: 75/100 (Good) โ โ โ โ โ Gateway bound to loopback โ โ โ No exposed API keys in config โ โ โ ๏ธ exec sandbox mode: unrestricted โ โ โ ๏ธ agentToAgent allow: * (too permissive) โ โ โ File permissions too open (644 โ should be 600) โ โ โ Heartbeat configured โ โ โ Session reset policy active โ โ โ ๏ธ No context pruning configured โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.