90/ 100
No threats observedNo threats observed: The observed run recorded no adverse findings. Scanned 23 Oct 2026.
Score
90 / 100Nothing was taken off for what the code did or what running it showed.
What it did
203 events in 31.3sNetwork
nothing real left the machineShow all 165 calls
Luna's report
The observed run and listed code checks had no adverse findings. Pin the scanned version. The entry phase timed out, 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 run was observed; no adverse findings were listed.
What it ran
Jev's answers
answered from the evidenceShow all 4 answers
Show all 3 answers
Not 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
Entry phase did not complete (timeout), so later behaviour was not observed
Reputation
Shown apart from the code and behaviour findings.