80/ 100
Low riskPartial runLow risk: The repository was reviewed, but its code was not run. Scanned 23 Oct 2026.
Nothing to build: no package.json, go.mod, Cargo.toml, pyproject.toml, setup.py, requirements.txt or Makefile
Score
100 − 10 = 80Points taken off
−10What it did
26 events in 20.9sLuna's report
The review found no malicious or suspicious flagged code, but the code was not run. Pin the scanned version before using it. The most important limit is that the entry phase was skipped, so its behaviour was not observed.
We scanned the repository’s code, but it had no install step the sandbox could run. The package was not installed and its entry point was not run, so sandbox behaviour was not observed.
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 5 items
Payloads gated on calendar dates past the accelerated clock window, or on hosts that need real responses
Install: the repo has no install step the sandbox runs (no package.json, go.mod, Cargo.toml, pyproject.toml, setup.py, requirements.txt or Makefile), so its code was read, not run
Entry phase was skipped, so its behaviour was not observed
Reputation
Shown apart from the code and behaviour findings.