nivo
nivo provides a rich set of dataviz components, built on top of the awesome d3 and React libraries
Runssource: GitHubhomepageTypeScriptMITcommit 0dae2c32052a
TypeScript, MIT licensed. The project labels itself: canvas, charts, components, d3js, dataviz, isomorphic, react and svg.
nivo runs. An Argusic agent installed it in 52 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm install succeeded, all 45 @nivo packages build (CJS+ESM), type check passes, all 47 test suites pass (739 tests, 39 snapshots), and the nivo API server runs on port 3030 serving chart SVG renders from POST /nivo/charts/bar and GET /nivo/r/* with valid SVG output
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 95 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.
- CJS/ESM interop failure: rollup-built CJS bundles require() ES Module d3 packages (d3-interpolate, d3-scale, d3-shape, etc.) on Node 18, causing ERR_REQUIRE_ESM.35 minutes
- Install time
- 52 minutes
- Cold machine to finish
- 52 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- curl -s -o /dev/null -w '%{http_code}' http://localhost:3030/status returned 200; curl -s -X POST http://localhost:3030/nivo/charts/bar returned 201 with a render URL; GET that URL returned 200 with valid SVG content; make pkgs-test exited 0 with 47 suites, 739 tests, 39 snapshots passed
- Model tokens used
- 508,626
- Exact commit tested
- 0dae2c32052a
- 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.
- Unknown chart types return 404 **Errors hit:** - CJS/ESM interop: `require()` of ES Module d3 packages from rollup CJS bundles. Fixed by removing … exec /bin/sh -lc '# Calculate time since start echo "Start: 20:54, now: $(date +%H:%M)"' in /work/repo succeeded in 0ms: Start: 20:54, now: 21:46 Total elapsed time is about 52 minutes. Let me compile the final result. tokens used 508,626 Total elapsed time is about 52 minutes. Let me compile the final result.
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 52 minutes.
- Recovered from all 1 error 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/nivo)Questions
- Does nivo run?
- Yes. nivo runs. Argusic installed and launched it on a clean machine in 52 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test nivo?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0dae2c32052a. 4 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test nivo?
- The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does nivo take to install?
- 52 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 nivo need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing nivo?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for nivo?
- 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.