safe-openclaw

Security-hardened OpenClaw with mandatory authentication, AES-256 encryption, session management, and secret redaction. Drop-in replacement, zero migration cost.

GitHub release npm version MIT License

The Problem

OpenClaw ships with zero authentication and stores API keys in plaintext. Deploy it on a server and anyone who discovers your URL owns your AI gateway — and every API key in it.

What safe-openclaw Adds

Mandatory Auth Gateway

Password-protected access with strong password policy enforcement. No anonymous access possible.

AES-256-GCM Encryption

API tokens encrypted at rest with AES-256-GCM. Keys are never stored in plaintext.

Session Management

HMAC-based session tokens with configurable expiry. Auto-restart on password change.

Secret Redaction

Automatic filtering of sensitive information in outbound messages and logs.

Localhost-Only Endpoints

Sensitive management endpoints restricted to localhost access only.

Security Shield Plugin

Built-in dangerous command blocking, secret leak detection in tool output, and full audit logging for all AI tool calls.

Drop-in Replacement

One command to upgrade. Your config, sessions, and channels are fully preserved.

Install

curl -fsSL https://raw.githubusercontent.com/Yapie0/safe-openclaw/main/install.sh | bash

Or install via npm:

npm install -g safe-openclaw