90/ 100
No threats observedNo threats observed: The observed run produced no behaviour deductions; reachable code still had flagged locations not seen in action. Scanned 23 Oct 2026.
Score
90 / 100Nothing was taken off for what the code did or what running it showed.
What it did
488 events in 30.6sNetwork
nothing real left the machineShow all 200 calls
Luna's report
The run showed no behaviour findings, but flagged code was not seen in action and one code window was judged suspicious. Pin the scanned version. Most important limit: behaviour outside the observed install and entry windows was not verified.
We installed the repository and ran its entry point in a throwaway sandbox, while scanning the code the entry point could reach. The run produced no behaviour findings; the repository's own install script failed after its dependencies installed.
What it ran
Jev's answers
answered from the evidenceShow all 5 answers
package.jsonShow 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
The repo's own install script failed after its dependencies installed (the repo's own lifecycle script failed (exit 1): /work/src postinstall: `simple-git-hooks` exited with exit status: 127); what ran before it was observed and scored
Reputation
Shown apart from the code and behaviour findings.