Moving Icons
beautifully crafted, moving icons. for svelte. 🧡
Runssource: GitHubhomepageSvelteMITcommit eebffac1dc79
Svelte, MIT licensed. The project labels itself: animation, iconset, svelte, sveltekit, svg animations and svg icons.
Moving Icons runs. An Argusic agent installed it in 12 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The @jis3r/icons Svelte 5 project builds, all 1120 unit tests pass, and the dev server starts and responds with HTTP 200
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 100 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- engine-strict=true in .npmrc blocks npm install on Node 18 (required Node >=20 for many transitive deps)3 minutes
- svelte-kit sync fails on Node 18: rolldown requires node:util.styleText (Node 22+)2 minutes
- Install time
- 12 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm test via 'npx vitest run' with Node 20 exited 0, 3 test files passed, 1120 tests passed; 'npx vite build' succeeded; dev server on port 5678 returned HTTP 200
- Model tokens used
- 48,707
- Exact commit tested
- eebffac1dc79
- 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.
sleep 4
curl -s -o /dev/null -w '%{http_code}' http://localhost:5678/ 2>&1
kill %1 2>/dev/null" in /work/repo
exited 1 in 14459ms:
VITE v8.0.16 ready in 792 ms
➜ Local: http://localhost:5678/
➜ Network: use --host to expose
200
The dev server responds with HTTP 200. Now let me clean up and finalize.
tokens used
48,707
The dev server responds with HTTP 200. Now let me clean up and finalize.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 12 minutes.
- Recovered from all 2 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 4 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/moving-icons)Questions
- Does Moving Icons run?
- Yes. Moving Icons runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test Moving Icons?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit eebffac1dc79. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test Moving Icons?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Moving Icons take to install?
- 12 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 Moving Icons need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Moving Icons?
- 2 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 Moving Icons?
- All 4 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.