ClaudeRabbit
New scan
github.com/openclaw/openclaw · c3b57f7

87/ 100

Low risk

Low risk: The observed install activity was limited, but installation failed and the entry phase did not complete. Scanned 23 Oct 2026.

NetworkNone
No network calls
Files1 change
/home/cr/.local/share/…f56bf6/_tmp_4667_32187b3c
CodeNothing taken off
no code deduction

Score

87 / 100
1000

Nothing was taken off for what the code did or what running it showed.

What it did

41 events in 73.0s
Fetched32.4s
187699222 bytes fetched inside the VM from codeload.github.com in 28797 ms; commit id verified; egress restored
Read59.9s
0 scanner finding(s)
Checked60.9s
417 locked dependencies, 0 malicious
Jev69.3s
Answered questions from the evidence
Sandbox69.3s
install completed, entry failed, 0 forged call(s)
Score69.3s
87 Low risk

Luna's report

The verdict is Low risk, but the entry phase did not complete and flagged code was not observed running. Pin the scanned version. Most importantly, later entry-point behaviour was not verified.

We installed the repository in a throwaway sandbox and scanned code used by its install process and entry point. Dependencies installed, but the repository’s preinstall script failed, so the entry point did not run to completion.

What it ran

Installedpnpm · 0.5s
Entry pointenv -i HOME=/hom…T=1 FAKETIME_NO_CAC
NetworkNo calls
MachineDestroyed after the scan

Jev's answers

answered from the evidence
Install check
Install-time code does not use the network
Install-time code does not read credentials
Show all 8 answers
Install-time code runs other programs or payloads
Install-time code is not obfuscated
Jev judged this code harmlesspackage.json
Jev judged this code harmlessscripts/prepare-git-hooks.mjs
Jev judged this code harmlessscripts/lib/package-lifecycle-marker.mjs
Jev judged this code harmlessscripts/runtime-postbuild-shared.mjs
Docs check
The docs do not say it makes no network calls
The docs do not say it has no side effects
Show all 3 answers
What it did goes beyond what its docs say it is for
Flagged code check
Jev judged this code harmless

Not verified

Behaviour outside the observed install and entry windows

Code paths not triggered by install or the entry point

Show all 7 items

Payloads gated on calendar dates past the accelerated clock window, or on hosts that need real responses

Flagged code that was read but never seen doing anything in the sandbox, so it takes no points: 48 reachable finding location(s), -268 floored at -40. (-5: Code reads the npm login token file at .agents/skills/openclaw-live-updater/scripts/update-main.mjs:88 (install); -5: Code reads the npm login token file at .agents/skills/telegram-e2e-userbot/scripts/published-upgrade-scenario.mjs:304 (install); -5: A shell script downloads and runs code from an unrecognised source at node-version.mjs:27 (install))

The repo's own install script failed after its dependencies installed (the repo's own lifecycle script failed (exit 1): . preinstall: Failed); what ran before it was observed and scored

Entry phase did not complete (failed), so later behaviour was not observed

Key-shaped strings in 154 files, never seen leaving the machine

Reputation

GitHubOwner 9 months old
GitHubOwner not established
GitHub393K stars
GitHub97 public repos

Warning: the owner has little public history.

Reputation warnings are shown on their own and do not lower the code score.

Shown apart from the code and behaviour findings.