ClaudeRabbit
New scan
npmjs.com/package/commander · 15.0.0+

90/ 100

No threats observed

No threats observed: The install and entry point ran with full coverage and no deductions. Scanned 23 Oct 2026.

Watch how it happenedScan another
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

33 events in 15.9s
Fetched0.2s
52736 bytes
Checked0.2s
0 locked dependencies, 0 malicious
Read7.3s
2 scanner finding(s)
Jev12.0s
Answered questions from the evidence
Sandbox12.0s
install completed, entry completed, 0 forged call(s)
Score12.5s
90 No threats observed

Luna's report

No threats observed in the covered run. Pin the scanned version. The run did not verify behaviour outside the observed install and entry windows.

We installed the package and ran its entry point in a throwaway sandbox, then scanned the code the entry point could reach. The run had full coverage, and the forge recorded no contact outside package registries, decoy credential reads or persistence writes.

What it ran

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

Jev's answers

answered from the evidence
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
Install check
Install-time code does not use 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

Not verified

Behaviour outside the observed install and entry windows

Code paths not triggered by install or the entry point

Show all 3 items

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

Reputation

npmWeekly npm downloads: 313640187
npmFirst npm publish: 5548 days ago
npmNo maintainer change within 30 days
npmFirst published 15 years ago
npmnpm maintainers: shadowspawn, abetomo
npm314M weekly downloads

Shown apart from the code and behaviour findings.