grist-core
Grist is the evolution of spreadsheets.
Runssource: GitHubhomepageTypeScriptApache-2.0commit 298d4661ce35
TypeScript, Apache-2.0 licensed. The project labels itself: awesome, database and spreadsheet.
grist-core runs. An Argusic agent installed it in 37 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Grist server starts and serves HTTP on port 8484 (returned 200); all unit/server/API test suites pass; Python formula sandbox is set up; Node 22 binary at /tmp/node-v22.12.0-linux-x64/bin/node is required.
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.
- System Node.js v18.19.1 too old for project's dependencies (requires >=20.17.0)5 minutes
- Install time
- 37 minutes
- Cold machine to finish
- 38 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- curl -sL http://localhost:8484/ returned 200 with Grist HTML page; 780 common tests passed; 138 gen-server API tests passed; 60 server tests passed
- Model tokens used
- 137,250
- Exact commit tested
- 298d4661ce35
- 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.
137,250 ## Report Here's the full summary of what I did and found: **Environment**: Node 18.19.1 default in container, but `.nvmrc` says `v22.12.0`. Downloaded Node 2… **Install**: `yarn install` + `yarn run install:python` succeeded with Node 22 + community edition.… **Verification**: - Common tests: `yarn run test:common` — **780 passing, 15 pending** - Gen-server API tests: `mocha _build/test/gen-server/ApiServer.js` — **138 passing, 1 pending** - Server test (Comm): `mocha _build/test/server/Comm.js` — **60 passing** - App launch: `curl -sL http://localhost:8484/` returned **200** and served Grist's full HTML landi… **Note**: Some tests are pending (e.g., python3 sandbox tests need a separate runner; nbrowser test… ```
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 37 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 Apache-2.0, as reported by its host.
- Measured 3 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/grist-core)Questions
- Does grist-core run?
- Yes. grist-core runs. Argusic installed and launched it on a clean machine in 37 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test grist-core?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 298d4661ce35. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test grist-core?
- The run that produced this verdict cost $0.26: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does grist-core take to install?
- 37 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 grist-core need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing grist-core?
- 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 grist-core?
- All 3 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.