90/ 100
No threats observedNo threats observed: The run scored 90; the entry phase did not complete. Scanned 29 Oct 2026.
Score
90 / 100Nothing was taken off for what the code did or what running it showed.
What it did
40 events in 26.5sLuna'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
Jev's answers
answered from the evidenceShow all 5 answers
package.jsonShow 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 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
Shown apart from the code and behaviour findings.