Argusic could not verify that melonJS runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 7 errors on the way, and recorded the session.

How did Argusic test melonJS?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 88402bc76f70. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test melonJS?

The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does melonJS take to install?

3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Does melonJS need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing melonJS?

7 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for melonJS?

All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

melonJS

a modern & lightweight HTML5 game engine

Could not verifysource: GitHub homepageJavaScriptMITcommit 88402bc76f70

JavaScript, MIT licensed. The project labels itself: 2d game engine, canvas2d, contributions welcome, es6, game development, game engine, gamedev and hacktoberfest.

Argusic could not get melonJS running. An Argusic agent installed it in 3 minutes and hit 7 errors on a clean machine with no GPU, and the whole session was recorded.

pnpm install and pnpm build succeed cleanly; the full vitest+playwright chromium test suite runs with 7132/7157 tests passing, 21 skipped, and 4 pre-existing environmentally-specific failures (2 SwiftShader timeouts, 1 font metrics mismatch, 1 gradient rendering difference, 1 async race condition).
What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 35.7 of 100 (the mean of this project's run scores).

At a glance

verdict: Could not verify
Argusic Score: 35.7 / 100
cost of the verifying run: $0.11 (measured)
recorded runs: 2
last tested: 2026-09-29
stars: 6,401
forks: 661
open issues: 20
watchers: 168
size: 141 MB
created: 2011-04-11
last push: 2026-09-27

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-29. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing melonJS, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Container had Node.js v18 but project requires >=242 minutes
Playwright browsers not installed1 minute
drawmesh_bench.spec.js timeout: SwiftShader software rasterization too slow (test timed out at 45s, needed ~198s)
renderable-transform.spec.js hook timeout: beforeAll creating WebGL context took >90s on SwiftShader
font.spec.js wordWrap test: expected measureText width <=100, got 110 (DejaVu Sans metrics different from Arial)
text-gradient.spec.js: gradient top-color comparison fails due to font-rendering differences in headless Chromium

Install time: 3 minutes
Cold machine to finish: 29 minutes
Errors hit and fixed: 7 hit, 2 fixed with no human help
How the result was proved: pnpm build exited 0 with 8/8 tasks successful. npx vitest --config packages/melonjs/vitest.config.ts exited 1 with '5 failed | 291 passed (296) Test Files, 4 failed | 7132 passed | 21 skipped (7157) Tests'
Model tokens used: 152,611
Exact commit tested: 88402bc76f70
Container image: sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory: this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run: each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

exec
/bin/sh -lc 'export PATH="/tmp/node-v24.0.0-linux-x64/bin:$PATH" && cd /work/repo && node -e "const…
 succeeded in 0ms:
{"name":"melonjs-monorepo","version":"0.0.0","engine":{"node":">=24.0.0"}}
Now I have a complete picture of the repository's state. Here's the final report:
**Installation**: Required downloading Node.js v24 (container had v18) and installing pnpm. `pnpm i…
**Tests**: 291/296 files passed, 7132/7157 tests passed, 4 failed, 21 skipped. All 5 failures are p…
tokens used
152,611
Now I have a complete picture of the repository's state. Here's the final report:
**Installation**: Required downloading Node.js v24 (container had v18) and installing pnpm. `pnpm i…
**Tests**: 291/296 files passed, 7132/7157 tests passed, 4 failed, 21 skipped. All 5 failures are p…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

Installed in 3 minutes.
Licensed MIT, as reported by its host.
Measured 2 times, so the result is not a one-off.

What did not, or is not known

An agent with no time limit did not get it running.
Hit 7 errors during setup, 5 of which were not solved.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Did not run	35.71	0.11	2026-09-29 00:12 UTC
Argusic Runner	1/3	Ran out of time	0.00	0.18	2026-09-28 23:43 UTC

Topics (from GitHub)

2d-game-engine canvas2d contributions-welcome es6 game-development game-engine gamedev hacktoberfest html5 html5-canvas javascript melonjs tiled typescript web3 webaudio webgl webgpu

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/melonJS.svg)](https://argusic.com/subject/melonjs)

Questions

Does melonJS run?: Argusic could not verify that melonJS runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test melonJS?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 88402bc76f70. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test melonJS?: The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does melonJS take to install?: 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does melonJS need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing melonJS?: 7 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for melonJS?: All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.