github.com/Ragnt/AngryOxide · 97517b4

74/ 100

CautionPartial run

Caution: The build failed before the program ran, leaving install and runtime behaviour unobserved. Scanned 25 Oct 2026.

Build failed, so the program never ran

Watch how it happened Scan another

NetworkNone

No network calls

CodeNothing taken off

no code deduction

Score

100 − 16 = 74

1000

Partial scan: Build fa…he score is capped at 74. −16

Points taken off

−16

Partial scan: Build failed, so the program never ran, so the score is capped at 74.

What it did

30 events in 20.9s

Fetched8.1s

3320086 bytes fetched inside the VM from codeload.github.com in 3262 ms; commit id verified; egress restored

Read13.7s

2 scanner finding(s)

Checked13.7s

0 locked dependencies, 0 malicious

Jev17.0s

Answered questions from the evidence

Sandbox17.0s

install failed, entry skipped, 0 forged call(s)

Score17.0s

74 Caution

Luna's report

The build failure left install and runtime behaviour unverified. Read the flagged code first, and note that the entry point was skipped.

We fetched and checked the package, then tried to install it in a throwaway sandbox and scan its reachable code. The build failed, so the program did not run and 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 phase did not complete (failed), so later behaviour was not observed

Entry phase was skipped, so its behaviour was not observed

Reputation

GitHubOwner 9 years old

GitHubOwner established (over a year, 3+ public repositories)

GitHub2K stars

GitHub14 public repos

Shown apart from the code and behaviour findings.