Recordsnpmsocket.io-client4.8.1Socket.volatile
Change the conditions
Current conditions
Socket.volatile @4.8.1alpine musl · x64 · node 22 · npm · node
1 of 1 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
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-23
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.8.1
linux · node@22.23 · moduleSystem=cjs · executionContext=node
9 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| debug | 4.3.7 | CANDIDATE Correlated change; unproven combination | 5 project-days | |
| @socket.io/component-emitter | 3.1.2 | UNKNOWN No linked outcome measured | 6 project-days | |
| engine.io-client | 6.6.6 | UNKNOWN No linked outcome measured | 5 project-days | |
| socket.io-parser | 4.2.7 | UNKNOWN No linked outcome measured | 4 project-days |
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.
| Library | 4.8.3 | 4.8.1 |
|---|---|---|
| debug | 4.4.3 | 4.3.7 |
| @socket.io/component-emitter | 3.1.2 | 3.1.2 |
| engine.io-client | 6.6.6 | 6.6.6 |
| socket.io-parser | 4.2.7 | 4.2.7 |
| ws | 8.21.3 | — |
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.
Recent failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×9 4.8.1 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-30Diagnostic re-verification candidate