ClaudeRabbit
New scan
github.com/PixelPlayerHQ/PixelPlayer · 63cb59b

80/ 100

Low riskPartial run

Low risk: The repository had no supported install or run step, so its code was read but not executed. Scanned 23 Oct 2026.

Nothing to build: no package.json, go.mod, Cargo.toml, pyproject.toml, setup.py, requirements.txt or Makefile

NetworkNone
No network calls
CodeNothing taken off
no code deduction

Score

100 − 7 = 80
1000
Partial scan: Nothing …g the code: capped at 80. −7

Points taken off

−7
−7
Partial scan: Nothing to build: no package.json, go.mod, Cargo.toml, pyproject.toml, setup.py, requirements.txt or Makefile. Nothing ran in the sandbox, so the score rests on reading the code: capped at 80.

What it did

26 events in 29.2s
Fetched5.5s
12118586 bytes fetched inside the VM from codeload.github.com in 3074 ms; commit id verified; egress restored
Read24.0s
0 scanner finding(s)
Checked24.0s
0 locked dependencies, 0 malicious
Jev26.1s
Answered questions from the evidence
Sandbox26.1s
install none, entry skipped, 0 forged call(s)
Score26.1s
80 Low risk

Luna's report

Low risk reflects a code review only, not a sandbox run. Pin the scanned version. The most important limit is that install and entry-point behaviour was not observed.

We checked the repository’s code, but it had no supported build or install step, so we did not install it or run its entry point in a throwaway sandbox. Sandbox behaviour was not observed.

What it ran

InstalledNothing to install
Entry pointNone found
NetworkNo calls
MachineDestroyed after the scan

Jev's answers

answered from the evidence
Install check
Install-time code does not use the network
Install-time code does not read credentials
Show all 4 answers
Install-time code does not run other programs or payloads
Install-time code is not obfuscated
Docs check
The docs do not say it makes no network calls
The docs do not say it has no side effects
Show all 3 answers
What it did fits what its docs say it is for

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

GitHubOwner 4 months old
GitHubOwner not established
GitHub6.8K stars
GitHub2 public repos

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.