SysGuard

What to check before installing: - The code appears to implement the advertised monitoring features, but review and (if needed) remove or replace the hardcoded external host (api.minimaxi.com) used for the 'API 响应超时' check — if you don't trust that host, it should be changed or removed. - Configure notification webhooks (FEISHU_WEBHOOK_URL / WECOM_WEBHOOK_URL) carefully — these receive system status and diagnostics. Only set them to endpoints you control. - Verify default paths (OPENCLAW_ROOT, DATA_DISK, BACKUP_ROOT, CONFIG_FILE) are appropriate for your system; the defaults point to /root/.openclaw and /mnt/vdc which might not exist or be sensitive. - The scripts call utilities such as curl, ping, pgrep, journalctl, bc and optionally jq; ensure those are available and acceptable on your host. 'jq' is required for trend charts if you want that feature. - The cleaner runs journalctl --vacuum-time and deletes files in /tmp/openclaw and historical JSONs; review the clean.sh logic and retention settings (HISTORY_RETENTION_DAYS) to avoid unintended deletions. - Run the scripts in a staging environment first and inspect what data is written and what network calls are made (especially outbound requests to webhooks and api.minimaxi.com). If you need, ask the author to document the api.minimaxi.com purpose or replace it with a configurable probe target. Overall: functionally coherent, but the undocumented external probe and a few imprecise claims ("zero-dependency") are reasons to inspect and possibly adjust configuration before production use.