89/ 100
Low riskLow risk: The observed run had no listed behaviour or dependency hits, with three flagged code locations not verified. Scanned 23 Oct 2026.
Score
100 − 1 = 89Points taken off
−1What it did
552 events in 36.7sNetwork
nothing real left the machineShow all 22 calls
Luna's report
The result was Low risk, but three flagged code locations were not seen doing anything in the sandbox. Pin the scanned version. The most important limit is that behaviour outside the observed install and entry windows was not verified.
We installed the package and ran its entry point in a throwaway sandbox, and scanned the reachable code. The run completed with a full record; pattern checks flagged three SSH-key locations in shell/completion.bash, judged benign by our code review.
What it ran
Jev's answers
answered from the evidenceShow all 3 answers
Show all 4 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
Flagged code that was read but never seen doing anything in the sandbox, so it takes no points: 3 reachable finding location(s). (-12: Code reads SSH private keys at shell/completion.bash:535 (import); -12: Code reads SSH private keys at shell/completion.bash:542 (import); -12: Code reads SSH private keys at shell/completion.bash:559 (import))
Reputation
Shown apart from the code and behaviour findings.