CodeSampleX

Recordsnpmsocket.io-client4.8.3WebSocketServer

Change the conditions
Fixed
Package version4.8.3 SymbolWebSocketServer
Filter OSalpine musl Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

WebSocketServer @4.8.3alpine musl · x64 · node 22 · npm · node

2 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
1 / 1
Contract verifications
2 / 2
Independent reporting peers
1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-07

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 4

Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
debug 4.4.3 CHANGED Version changed, no linked failure contract passed 1 project-day
@socket.io/component-emitter 3.1.2 PASS All observations passed contract passed 1 project-day
engine.io-client 6.6.6 PASS All observations passed contract passed 1 project-day
socket.io-parser 4.2.7 PASS All observations passed contract passed 1 project-day
ws 8.21.3 PASS All observations passed contract passed 1 project-day

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 1 · unchanged at every release: 4

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.