80/ 100
Low riskPartial runLow risk: The build finished, but the entry phase was skipped. Scanned 23 Oct 2026.
Build finished, but there was no program to run
Score
100 − 5 = 80Points taken off
−5What it did
30 events in 15.4sLuna's report
The build completed, but the entry phase was skipped, so its behaviour was not observed. Pin the scanned version; the most important limit is that entry-phase behaviour was not verified.
We installed the package in a throwaway sandbox and scanned its code, but there was no program to run. The build finished; the entry point was not run.
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
Entry phase was skipped, so its behaviour was not observed
Reputation
Shown apart from the code and behaviour findings.