90/ 100
No threats observedNo threats observed: The observed run produced no negative findings, with reputation points raising the score to 90. Scanned 23 Oct 2026.
Score
90 / 100Nothing was taken off for what the code did or what running it showed.
What it did
35 events in 29.7sLuna's report
No threats observed is based on the observed run and supplied code review results, not untested paths. Pin the scanned version. Most important limitation: the entry phase failed, so later behaviour was not observed.
We installed the package and ran its entry point in a throwaway sandbox, and scanned the reachable code. The observed run produced no negative behaviour findings.
What it ran
Jev's answers
answered from the evidenceShow all 3 answers
Show all 5 answers
package.jsonNot verified
Behaviour outside the observed install and entry windows
Code paths not triggered by install or the entry point
Show all 5 items
Payloads gated on calendar dates past the accelerated clock window, or on hosts that need real responses
Entry phase did not complete (failed), so later behaviour was not observed
Dev dependencies: install scripts run (0 packages), other code not executed (511 packages)
Reputation
Shown apart from the code and behaviour findings.