90/ 100
No threats observedNo threats observed: The install and entry point ran with full coverage and no deductions. Scanned 23 Oct 2026.
Score
90 / 100Nothing was taken off for what the code did or what running it showed.
What it did
281 events in 99.2sLuna's report
No threats were observed in the covered run, but untriggered paths and later or host-dependent payloads were not verified. Pin the scanned version; the most important limit is behaviour outside the observed install and entry windows.
We installed the package and ran its entry point in a throwaway sandbox, then scanned the reachable code. The run had full coverage and recorded no contact outside package registries, decoy credential reads or persistence writes.
What it ran
Jev's answers
answered from the evidenceShow all 3 answers
Show all 4 answers
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
Shown apart from the code and behaviour findings.