90/ 100
No threats observedNo threats observed: The package’s observed install and entry-point run produced no score deductions. Scanned 23 Oct 2026.
Score
90 / 100Nothing was taken off for what the code did or what running it showed.
What it did
159 events in 20.6sNetwork
nothing real left the machineShow all 126 calls
Luna's report
No threats observed in the covered run. 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 code reached from the entry point. Both phases completed with full coverage; no behaviour deductions were recorded.
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 (0 packages)
Reputation
Shown apart from the code and behaviour findings.