87/ 100
Low riskLow risk: No credential exfiltration was recorded, but the entry phase timed out. Scanned 23 Oct 2026.
Score
87 / 100Nothing was taken off for what the code did or what running it showed.
What it did
234 events in 37.1sNetwork
nothing real left the machineShow all 196 calls
Luna's report
The install script contains code our code review judged suspicious, while the entry phase timed out. Read the flagged code before using this Low risk package; behaviour after the timeout was not verified.
We installed the package and ran its entry point in a throwaway sandbox, while scanning reachable code. The install ran, but the entry phase timed out, so later behaviour was not observed.
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 6 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: 23 reachable finding location(s), -185 floored at -40. (-5: A shell script downloads and runs code from an unrecognised source at deploy/posthog/posthog-hetzner-prep.sh:101 (import); -12: Code contacts a hard-coded internet address at scripts/install/install.sh:257 (import); -12: A shell script downloads and runs code from an unrecognised source at scripts/install/install.sh:2 (import))
Entry phase did not complete (timeout), so later behaviour was not observed
Key-shaped strings in 15 files, never seen leaving the machine
Reputation
Warning: the owner has little public history.
Reputation warnings are shown on their own and do not lower the code score.
Shown apart from the code and behaviour findings.