OpenClaw Update Checker

• Verdict: Pass
• Analyzed: May 12, 2026, 4:30 AM
• Findings: 0
• Version: 1.1.1
• Hash: bc42c6b61faad63a506f9fa0e077419c7f58a5577b2e8cd661c18d9f88c37642
• Source: palm
• External report: View on VirusTotal

Overview

Type: OpenClaw Skill Name: openclaw-update-checker Version: 1.1.1 The OpenClaw Update Checker skill is benign. Both the `SKILL.md` documentation and the `scripts/check_update.py` code consistently describe and implement a read-only operation. The skill only reads specific `package.json` files at hardcoded paths (`/usr/lib/node_modules/openclaw/package.json`, `/usr/local/lib/node_modules/openclaw/package.json`) and performs a single HTTPS GET request to the public npm registry (`https://registry.npmjs.org/openclaw`). The Python script uses only standard library functions (`pathlib`, `urllib.request`, `json`, `re`) and explicitly avoids subprocess execution, file writing, or any other system modifications. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts against the agent.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

ASI02: Tool Misuse and Exploitation

NoteHigh Confidence

What this means

Running the skill will contact npm and inspect local OpenClaw package metadata, but the artifacts show no file writes or update actions.

Why it was flagged

The skill uses local file reads and an outbound registry request; these are clearly disclosed and aligned with checking the installed version against npm.

Skill content

**File reads:** `/usr/lib/node_modules/openclaw/package.json` and `/usr/local/lib/node_modules/openclaw/package.json` ... **Network:** Single HTTPS GET to `https://registry.npmjs.org/openclaw`

Recommendation

Use it when you are comfortable with a public npm registry lookup; no extra permissions or credentials appear necessary.

ASI04: Agentic Supply Chain Vulnerabilities

NoteHigh Confidence

What this means

There is less external provenance information than ideal, although the supplied source is short and consistent with the stated behavior.

Why it was flagged

The registry metadata does not provide an upstream source or homepage, so users must rely on the included artifacts for provenance review.

Skill content

Source: unknown
Homepage: none

Recommendation

Review the included script before installing if provenance matters in your environment.