ClaudeRabbit
New scan
npmjs.com/package/Hello · 0.0.1+s

80/ 100

Low riskPartial run

Low risk: The build finished, but the entry phase was skipped. Scanned 23 Oct 2026.

Build finished, but there was no program to run

NetworkNone
No network calls
CodeNothing taken off
no code deduction

Score

100 − 5 = 80
1000
Partial scan: Build fi…he score is capped at 80. −5

Points taken off

−5
−5
Partial scan: Build finished, but there was no program to run, so the score is capped at 80.

What it did

30 events in 15.4s
Fetched0.6s
1171 bytes
Checked0.6s
0 locked dependencies, 0 malicious
Read11.1s
1 scanner finding(s)
Jev11.9s
Answered questions from the evidence
Sandbox11.9s
install completed, entry skipped, 0 forged call(s)
Score12.4s
80 Low risk

Luna's report

The build completed, but the entry phase was skipped, so its behaviour was not observed. Pin the scanned version; the most important limit is that entry-phase behaviour was not verified.

We installed the package in a throwaway sandbox and scanned its code, but there was no program to run. The build finished; the entry point was not run.

What it ran

Installednpm · 1 package · 2.5s
Entry pointNone found
NetworkNo calls
MachineDestroyed after the scan

Jev's answers

answered from the evidence
Install check
Install-time code uses the network
Install-time code does not read credentials
Show all 5 answers
Install-time code does not run other programs or payloads
Install-time code is not obfuscated
Jev judged this code harmlesspackage.json
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 fits 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 4 items

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

Entry phase was skipped, so its behaviour was not observed

Reputation

npmWeekly npm downloads: 3
npmFirst npm publish: 3794 days ago
npmNo maintainer change within 30 days
npmFirst published 10 years ago
npmnpm maintainers: ajeesh13
npm3 weekly downloads

Shown apart from the code and behaviour findings.