90/ 100
No threats observedNo threats observed: The observed install run earned a score of 90, but the entry phase did not complete. Scanned 23 Oct 2026.
Score
90 / 100Nothing was taken off for what the code did or what running it showed.
What it did
246 events in 53.3sNetwork
nothing real left the machineShow all 200 calls
Luna's report
No threats observed is the verdict, but later entry behaviour was not observed. Pin the scanned version. Most importantly, the entry phase did not complete.
We installed the package and ran its entry point in a throwaway sandbox, and scanned the reachable code. The repository’s lifecycle script failed after dependencies installed, so the entry phase did not complete.
What it ran
Jev's answers
answered from the evidenceShow all 8 answers
package.jsonscripts/postinstall-native.jsscripts/verify-install.jsscripts/bundle-cli.mjsShow all 3 answers
Not verified
Behaviour outside the observed install and entry windows
Code paths not triggered by install or the entry point
Show all 8 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: 3 reachable finding location(s). (-5: A shell script downloads and runs code from an unrecognised source at src/surface/cli.ts:1326 (install); -5: A shell script downloads and runs code from an unrecognised source at src/surface/doctor.ts:1374 (install); -5: A shell script downloads and runs code from an unrecognised source at src/surface/installed-copies.ts:137 (install))
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 (214 packages)
fsevents 2.3.3: macOS-only, not run in this sandbox
Reputation
Shown apart from the code and behaviour findings.