saltcorn
Free and open source no-code application builder
Runssource: GitHubhomepageJavaScriptMITcommit c296aa3d463f
JavaScript, MIT licensed. The project labels itself: no code and nocode.
saltcorn runs. An Argusic agent installed it in 29 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
TypeScript compiles, all 1038 unit tests pass across three packages, and the Saltcorn server starts and responds on port 3099 with HTTP 302 redirect to /auth/create_first_user, ready for initial admin setup.
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.
- Static import of @saltcorn/sqlite-mobile/sqlite_capacitor in db/index.ts triggers ERR_REQUIRE_ESM on Node 18 (CJS module requiring ESM)3 minutes
- Node.js version 18.19.1 installed but project requires >=202 minutes
- Server cluster workers crash on SQLite backend2 minutes
- npm install fails with ERESOLVE due to @fonticonpicker/react-fonticonpicker requiring react 16 vs workspace react 181 minute
- Install time
- 29 minutes
- Cold machine to finish
- 44 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm run tsc compiled successfully; packages/saltcorn-markup/dist: node --test passed 133/133 (0 fail); packages/saltcorn-data/dist: node --test --test-concurrency=1 passed 859/859 (0 fail); packages/db-common/dist: node --test passed 46/46 (0 fail); saltcorn serve -p 3099 with SQLITE and NWORKERS=1 returned HTTP 302 redirecting to /auth/create_first_user
- Model tokens used
- 255,060
- Exact commit tested
- c296aa3d463f
- 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.
- `npm install` needs `--legacy-peer-deps` due to a react peer-dep mismatch in `@fonticonpicker/rea… - Server in cluster mode needs `SALTCORN_NWORKERS=1` to run on SQLite; otherwise workers crash. - CJS/ESM interop shims trigger experimental warnings but work correctly on Node 22. tokens used 255,060 All verified. Here's the final report: **Summary:** Saltcorn compiles, installs, passes all unit tests, and launches as a web server with … **Key findings:** - The monorepo requires Node.js >=20. The system had Node 18 — downloaded Node 22 and used it for b… - `npm install` needs `--legacy-peer-deps` due to a react peer-dep mismatch in `@fonticonpicker/rea… - Server in cluster mode needs `SALTCORN_NWORKERS=1` to run on SQLite; otherwise workers crash. - CJS/ESM interop shims trigger experimental warnings but work correctly on Node 22.
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 29 minutes.
- Recovered from all 4 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/saltcorn)Questions
- Does saltcorn run?
- Yes. saltcorn runs. Argusic installed and launched it on a clean machine in 29 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test saltcorn?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c296aa3d463f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test saltcorn?
- The run that produced this verdict cost $0.36: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does saltcorn take to install?
- 29 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 saltcorn need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing saltcorn?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for saltcorn?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.