ioBroker.javascript

Script engine for JavaScript and Blockly

Runs with mockssource: GitHubJavaScriptMITcommit 365fc600a9a4

JavaScript, MIT licensed. The project labels itself: blockly, home automation, iobroker, javascript, script engine and smarthome.

ioBroker.javascript runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 502 standalone unit tests pass, TypeScript backend compiles cleanly, Blockly generator snapshots match, FBD (76 tests) runs end to end, scheduler works, secrets and credentials resolve correctly, TypeScript compilation and tooling work, mirror file sync passes all path edge cases.

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.09 (measured)
recorded runs
1
last tested
stars
330
forks
122
open issues
133
watchers
22
size
444 MB
created
last push

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.

Time lost to each failure while testing ioBroker.javascript, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node.js v18.19.1 is too old (requires >=22.19.0)2 minutes
  • src-editor npm install failed due to peer dependency conflict (jsdom@30 vs blockly@13 requiring jsdom@>=27.4.0 <30.0.0)1 minute
Install time
2 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npx mocha with 18 test files, 430 tests passed in combined run; plus io-improvements.test.js (45 passed) and performance-improvements.test.js (27 passed) = 502 total. Backend TypeScript compilation (tsc -p tsconfig.build.json) exits 0 with no output. Declaration tests (tsc -p test/lib/TS + test/lib/JS) pass.
Model tokens used
272,557
Exact commit tested
365fc600a9a4
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
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

 succeeded in 1000ms:
> [email protected] test:declarations
> tsc -p test/lib/TS/tsconfig.json && tsc -p test/lib/JS/tsconfig.json
Everything works. Let me record the final result.
exec
/bin/sh -lc 'export PATH="/tmp/node-v22.19.0-linux-x64/bin:$PATH" && cd /work/repo && npx prettier …
 succeeded in 41ms:
3.9.9
Now let me compile the final summary. The Node.js version requirement was the main blocker — I reso…
tokens used
272,557
Now let me compile the final summary. The Node.js version requirement was the main blocker — I reso…

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

  • Installed in 2 minutes.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.09

Topics (from GitHub)

blocklyhome-automationiobrokerjavascriptscript-enginesmarthome

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/ioBroker.javascript.svg)](https://argusic.com/subject/iobroker-javascript)

Questions

Does ioBroker.javascript run?
ioBroker.javascript runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test ioBroker.javascript?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 365fc600a9a4. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test ioBroker.javascript?
The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ioBroker.javascript take to install?
2 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 ioBroker.javascript need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ioBroker.javascript?
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 ioBroker.javascript?
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.

Discussion