node-red-dashboard
Runssource: GitHubJavaScriptApache-2.0commit be2d2c1a9690
JavaScript, Apache-2.0 licensed. The project labels itself: data visualisation, data visualization, iiot, iot, low code and node red.
node-red-dashboard runs. An Argusic agent installed it in 1 minute and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
With Node.js 24.22.2, the project installs and builds, all 264 Mocha tests pass, the 217-test Cypress run completes with 216 passing and 1 pending, and Node-RED 4.1.16 serves the editor, Dashboard client, and setup endpoint 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. 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.
- Default Node.js 18.19.1 is unsupported by locked Mocha 12/Cypress 15 and other tooling; mocha failed with SyntaxError: Unexpected token 'with' and npm emitted EBADENGINE warnings.4 minutes
- Isolated Node-RED launch initially failed with node-red: not found, then ignored the plugin until it was installed in that user directory.2 minutes
- Initial blank Node-RED flow returned 404 for /dashboard and /dashboard/_setup because no ui-base config node existed.1 minute
- Cypress run modified tracked fixture config files.1 minute
- Install time
- 1 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm ci exited 0 after adding 1301 packages; npm run build exited 0; npm test reported 264 passing; npm run lint and npm run typecheck exited 0; npx cypress run --browser electron --headless exited 0 with 39 specs, 217 tests, 216 passing and 1 pending; curl returned 200 for /, /dashboard/, and /dashboard/_setup.
- Model tokens used
- 418,523
- Exact commit tested
- be2d2c1a9690
- 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.
--- docs 28:- [Node.js](https://nodejs.org/en/download) - Node.js 20.19 or newer is required. Node.js 24 is … --- final server 3 Nov 09:05:33 - [info] Server now running at http://127.0.0.1:1881/ 3 Nov 09:05:33 - [info] [ui-base:UI Name] Node-RED Dashboard 2.0 (v1.34.1) started at /dashboard 3 Nov 09:05:33 - [info] [ui-base:UI Name] Created socket.io server bound to Node-RED port at path /… editor=200 dashboard=200 setup=200 2026-11-03T09:06:14.274849Z ERROR codex_core::session: failed to record rollout items: thread 01a1a… tokens used 418,523
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 1 minute.
- 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 Apache-2.0, 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.
- A quick evaluation: it was running 1 minutes after the clone.
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/node-red-dashboard)Questions
- Does node-red-dashboard run?
- Yes. node-red-dashboard runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test node-red-dashboard?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit be2d2c1a9690. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test node-red-dashboard?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does node-red-dashboard take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does node-red-dashboard need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing node-red-dashboard?
- 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 node-red-dashboard?
- 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.