sprig

🍃 Learn to code by making games in a JavaScript web-based game editor.

Runssource: GitHubhomepageJavaScriptMITcommit 7c32a85a62a5

JavaScript, MIT licensed. The project labels itself: game, game development, game engine, hacktoberfest, learning and puzzle.

sprig runs. An Argusic agent installed it in 14 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The Sprig web editor app installs, builds, serves all routes with HTTP 200/302, and passes all 12 vitest unit tests on Node 22.

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 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.08 (measured)
recorded runs
2
last tested
stars
1,119
forks
1,945
open issues
66
watchers
15
size
125 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . 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 sprig, 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.

  • Bun not installed (no unzip available); used npm instead1 minute
  • npm peer-dep conflict on Node 18 (Cannot read properties of null reading edgesOut)1 minute
  • Node 18 unsupported by Astro 6 (requires >=22.12.0)1 minute
  • EMILE too many open files when watching (ulimit too low)
  • Missing react dependency for react-icons
Install time
14 minutes
Cold machine to finish
15 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
npx vitest run passed 12/12 tests (all passed); curl http://127.0.0.1:4999/ returned 200 (142059 bytes); /editor=302, /gallery=200, /login=200, /up=200, /sprigpedia=200; astro build completed
Model tokens used
79,272
Exact commit tested
7c32a85a62a5
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.

**What works:**
- `npm install` succeeds
- `astro build` succeeds
- Dev server starts and serves `/` (200, 142KB), `/editor` (302), `/gallery` (200), `/login` (200),…
- `vitest run` passes all 12 tests (2 test files, 12 tests)
- Engine tests (infinite loop detection, error normalization) and crypto tests all pass
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 1…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 14, "errors": [{"msg": "Bu…
tokens used
79,272

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

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 14 minutes, faster than the median of the 5 comparable projects Argusic has measured.
  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 6 game projects Argusic has installed and timed, sprig was the 2nd fastest to reach a running state, and 4 of 6 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.08
Argusic Runner1/3Did not run20.000.05

Topics (from GitHub)

gamegame-developmentgame-enginehacktoberfestlearningpuzzle

Embed the badge

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

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

Questions

Does sprig run?
Yes. sprig runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test sprig?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7c32a85a62a5. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test sprig?
The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does sprig take to install?
14 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 sprig need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing sprig?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does sprig compare with the alternatives?
Of the 6 game projects Argusic has installed and timed, sprig was the 2nd fastest to reach a running state, and 4 of 6 reached one at all.
Where is the evidence for sprig?
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.

Discussion