ClaudeRabbit
New scan
github.com/sindresorhus/is · e9c026c

90/ 100

No threats observed

No threats observed: The run scored 90; the entry phase did not complete. Scanned 29 Oct 2026.

NetworkNone
No network calls
CodeNothing taken off
no code deduction

Score

90 / 100
1000

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

What it did

40 events in 26.5s
Fetched3.6s
975575 bytes fetched inside the VM from codeload.github.com in 1865 ms; commit id verified; egress restored
Read12.3s
3 scanner finding(s)
Checked12.3s
0 locked dependencies, 0 malicious
Jev22.5s
Answered questions from the evidence
Sandbox22.5s
install completed, entry failed, 0 forged call(s)
Score22.5s
90 No threats observed

Luna's report

The result was No threats observed, but later entry behaviour was not observed because the entry phase failed. Pin the scanned version. Most importantly, behaviour outside the observed install and entry windows was not verified.

We installed the package and ran its entry point in a throwaway sandbox, and scanned the reachable code. The install script failed after dependencies installed, and the entry phase did not complete; earlier activity was observed.

What it ran

InstalledNothing to install
Skipped477 packages
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 5 answers
Install-time code runs other programs or payloads
Install-time code is not obfuscated
Jev judged this code harmlesspackage.json
Flagged code check
Jev judged this code harmless
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

Not verified

Behaviour outside the observed install and entry windows

Code paths not triggered by install or the entry point

Show all 6 items

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

The repo's own install script failed after its dependencies installed (the repo's own lifecycle script failed (exit 127): npm: prepare of /work/src failed); what ran before it was observed and scored

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

Dev dependencies: install scripts run (1 packages), other code not executed (477 packages)

Reputation

GitHubOwner 16 years old
GitHubOwner established (over a year, 3+ public repositories)
GitHub1.8K stars
GitHub1.1K public repos

Shown apart from the code and behaviour findings.