openclaw-safe-upgrade@1.0.0
CAUTION· static onlyPublisher claims: "Safe OpenClaw upgrade with instant rollback. Use when user says "upgrade openclaw", "update openclaw", "check for updates", or any request to upgrade/update..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-20 and scored it 64/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
if ! npm i -g openclaw@latest --no-fund --no-audit --loglevel=error 2>&1 | tee -a "$UPGRADE_LOG"; thenFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.- `/tmp/upgrade-live.log` for live outputFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.1. **Cgroup escape**: re-execs via `systemd-run --user --scope` so gateway stop can't kill the scriptFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.4. `npm i -g openclaw@latest`Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
16 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim aliahmadaziz: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Unpinned dependencies≈ +3 on the totalPin exact versions (and ideally hashes) in package.json, requirements or the install script so the bundle cannot change under you.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Unpinned dependency≈ +1 on the totalPin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.