Skip to content

Security: sulimanbadour1/OpenClaw_raspberry

Security

SECURITY.md

Security Notes

Secrets Handling

  • Do not commit API keys, tokens, or service credentials.
  • Store secrets in environment variables or local files excluded by .gitignore.
  • Use .env.example as a template only.

Sensitive Local Paths (Do Not Commit)

  • shell profile files containing exported secrets
  • OpenClaw runtime auth/token state files
  • user service environment override files

Before Pushing

Run:

git status
rg -n "(sk-[A-Za-z0-9]|API_KEY\\s*=|Bearer\\s+[A-Za-z0-9_-]{20,})" .
make security-check

Then confirm no real key values are present in tracked files.

Safe Env Workflow

cp .env.example .env
nano .env
./scripts/configure_env.sh --env-file .env --restart-gateway

This keeps real keys out of git while applying them to runtime services.

There aren't any published security advisories