OpenClaw Checkpoint - Personal AI Assistant Backup & Recovery (Github)

Backup and restore OpenClaw workspace state and agents across machines using git. Enables disaster recovery by syncing SOUL.md, MEMORY.md, memory files, cron...

This package is instruction-only and contains no scripts — it expects you to clone or download code from a third-party GitHub repository and run an install script (the README even suggests curl | bash). Before installing: (1) confirm the external GitHub repo and author are trustworthy; the registry lists 'Source: unknown' which is a red flag for provenance; (2) inspect the install script and any scripts/checkpoint* files locally before executing them — avoid blindly piping remote content to bash; (3) verify the repo's .gitignore and a dry-run of what will be committed, so secrets (API keys, .env files) are not accidentally pushed; (4) prefer SSH auth or a minimally-scoped GitHub token; (5) be aware the installer will modify your PATH and may add a user cron or launchd job for scheduled backups; (6) if you do want this functionality, consider cloning the repo yourself, reviewing all scripts, and only then running the setup commands. Because of the mismatch between claimed CLI tools and the absence of bundled code plus the recommended remote-install pattern, proceed cautiously and audit the external code before use.

Type: OpenClaw Skill Name: openclaw-checkpoint Version: 1.0.5 The OpenClaw Checkpoint skill is designed for legitimate backup and restore operations, explicitly excluding sensitive data like API keys and warning users about private repositories. However, it is classified as 'suspicious' due to several high-risk capabilities inherent in its design: the recommended 'quick install' method involves `curl -fsSL ... | bash`, which is a significant supply chain risk. The skill also extensively uses powerful shell commands (`git`, `cp`, `rsync`, `sed`, `grep`, `crontab`, `launchctl`) for file system manipulation, network communication, and persistence (via cron/launchd). While these are necessary for its stated purpose, they represent a broad attack surface for potential shell injection vulnerabilities if not meticulously sanitized in the underlying scripts (which are not provided for analysis). There is no evidence of intentional malicious behavior like data exfiltration to unauthorized endpoints or obfuscation, but the combination of `curl | bash` and broad system interaction warrants caution.