90/ 100
No threats observedNo threats observed: the install and entry point ran with full coverage and no recorded deductions. Scanned 24 Oct 2026.
Score
90 / 100Nothing was taken off for what the code did or what running it showed.
What it did
35 events in 27.9sLuna's report
No threats were observed in the covered run. Pin the scanned version. Behaviour outside the install and entry windows was not verified.
We installed the package and ran its entry point in a throwaway sandbox, and scanned the code it could reach. The run had full coverage and 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 4 items
Payloads gated on calendar dates past the accelerated clock window, or on hosts that need real responses
Dev dependencies: install scripts run (0 packages), other code not executed (159 packages)
Reputation
Shown apart from the code and behaviour findings.