socket.io
Bidirectional and low-latency communication for every platform
Runssource: GitHubTypeScriptMITcommit 1eaa582d3b45
TypeScript, MIT licensed. The project labels itself: javascript, nodejs, socket io and websocket.
socket.io runs. An Argusic agent installed it in 29.1 minutes and hit 9 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
9 of 12 workspace packages compile and pass tests on Node 18.19.1. WebTransport tests excluded (needs Node 20+ QUIC). uWebSockets.js tests conditionally skipped. 3 packages unverifiable without PostgreSQL/Redis.
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.
- engine.io-client test hooks failed: [email protected] uses bare 'crypto' global undefined in strict mode on Node 183 minutes
- engine.io WebTransport tests fail: native QUIC module (webtransport.node) cannot be built on Node 181.5 minutes
- socket.io tests fail: uWebSockets.js native binary incompatible with Node 181.5 minutes
- npm install (with scripts) failed: @fails-components/webtransport-transport-http3-quiche build.js uses 'import with' syntax unsupported by Node 181 minute
- npm ci failed: package-lock.json out of sync with package.json; missing puppeteer-core and chromium-bidi packages0.5 minutes
- engine.io-client WebTransport tests fail: same native module issue0.5 minutes
- Install time
- 29 minutes
- Cold machine to finish
- 30 minutes
- Errors hit and fixed
- 9 hit, 9 fixed with no human help
- How the result was proved
- npm test on 9 packages: engine.io-parser 29p, engine.io 177/176p, engine.io-client 83p, socket.io-parser 34p, socket.io-adapter 48p, socket.io-client 112p, socket.io 196p, @socket.io/component-emitter 16p, @socket.io/cluster-adapter 18p, all zero failures for non-infrastructure tests
- Model tokens used
- 172,168
- Exact commit tested
- 1eaa582d3b45
- 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.
}
},
+ "node_modules/@wdio/local-runner/node_modules/devtools-protocol": {
+ "version": "0.0.1608973",
+ "resolved": "https://registry.npmjs.org/devtools-protocol/-/devtools-protocol-0.0.1608973.tg…
+ "integrity": "sha512-Tpm17fxYzt+J7VrGdc1k8YdRqS3YV7se/M6KeemEqvUbq/n7At1rWVuXMxQgpWkdwSdIEKY…
+ "dev": true,
+ "optional": true,
2026-10-05T07:46:04.287716Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
tokens used
172,168
The results are confirmed from my earlier runs. Let me compute the final metrics and output the res…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.
- Recovered from all 9 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
- Took 29.1 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 javascript projects Argusic has installed and timed, socket.io was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
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/socket-io)Questions
- Does socket.io run?
- Yes. socket.io runs. Argusic installed and launched it on a clean machine in 29 minutes, hitting 9 errors on the way, and recorded the session.
- How did Argusic test socket.io?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1eaa582d3b45. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test socket.io?
- The run that produced this verdict cost $0.35: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does socket.io take to install?
- 29.1 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 socket.io need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing socket.io?
- 9 things broke in the recorded run, and 9 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does socket.io compare with the alternatives?
- Of the 4 javascript projects Argusic has installed and timed, socket.io was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for socket.io?
- 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.