89/ 100
Low riskLow risk: The run completed, while flagged code and limited coverage kept the score below the top tier. Scanned 23 Oct 2026.
Score
100 − 1 = 89Points taken off
−1What it did
238 events in 28.5sNetwork
nothing real left the machineShow all 200 calls
Luna's report
Low risk reflects the completed run, but flagged code and untested paths remain. Pin the scanned version. Most important: behaviour outside the observed install and entry windows was not verified.
We installed the package and ran its entry point in a throwaway sandbox, then scanned the code reached from it. The run completed with a full record and no reported behaviour hit.
What it ran
Jev's answers
answered from the evidenceShow all 3 answers
Show all 5 answers
pyproject.tomlNot 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
Flagged code that was read but never seen doing anything in the sandbox, so it takes no points: 8 reachable finding location(s), -54 floored at -40. (-5: A shell script downloads and runs code from an unrecognised source at containers/docker-entrypoint.sh:62 (import); -5: Code reads the npm login token file at strix/interface/cloud/billing.py:305 (import); -5: Code reads the npm login token file at strix/interface/cloud/billing.py:306 (import))
Key-shaped strings in 4 files, never seen leaving the machine
Reputation
Shown apart from the code and behaviour findings.