ClaudeRabbit
New scan
github.com/GyanD/codexffmpeg · e90aadc

80/ 100

Low riskPartial run

Low 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

NetworkNone
No network calls
CodeNothing taken off
no code deduction

Score

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

Points taken off

−10
−10
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 20.9s
Fetched5.8s
1110 bytes fetched inside the VM from codeload.github.com in 4550 ms; commit id verified; egress restored
Read15.0s
0 scanner finding(s)
Checked15.0s
0 locked dependencies, 0 malicious
Jev16.3s
Answered questions from the evidence
Sandbox16.3s
install none, entry skipped, 0 forged call(s)
Score16.3s
80 Low risk

Luna'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

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

Jev's answers

answered from the evidence
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
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

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 15 years old
GitHubOwner established (over a year, 3+ public repositories)
GitHub2.6K stars
GitHub5 public repos

Shown apart from the code and behaviour findings.