90/ 100
No threats observedNo threats observed: The observed run and code review found no flagged issues. Scanned 23 Oct 2026.
Score
90 / 100Nothing was taken off for what the code did or what running it showed.
What it did
78 events in 31.3sNetwork
nothing real left the machineShow all 39 calls
Luna's report
No threats observed in the recorded run, but behaviour outside the observed windows and code paths not triggered remain unverified. Pin the scanned version.
We installed the package and ran its entry point in a throwaway sandbox, and scanned the reachable code. The forge 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 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 (1 packages), other code not executed (558 packages)
Reputation
Shown apart from the code and behaviour findings.