90/ 100
No threats observedNo threats observed: The scan found no flagged code or behaviour in the observed run. Scanned 23 Oct 2026.
Score
90 / 100Nothing was taken off for what the code did or what running it showed.
What it did
106 events in 29.0sNetwork
nothing real left the machineShow all 64 calls
Luna's report
This result is No threats observed, based on the observed run and scanned code. Pin the scanned version. 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 run produced a complete record with no recorded 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 (2 packages), other code not executed (380 packages)
Reputation
Shown apart from the code and behaviour findings.