CodeSampleX

Recordsnpmsocket.io-client4.8.1

Change the conditions
Fixed
OSubuntu glibc
Filter Runtimenode 22 Package version4.8.1 Symbolwhole package Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

socket.io-client @4.8.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

14 of 23 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
14 / 23
Contract verifications
nothing at this coordinate
Usage records
22
Independent reporting peers
3
Failures with a captured fingerprint
0 / 9
Last recorded
2026-08-30

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 3

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 contract passed 5 project-days
@socket.io/component-emitter 3.1.2 PASS All observations passed contract passed 6 project-days
engine.io-client 6.6.6 PASS All observations passed contract passed 5 project-days
socket.io-parser 4.2.7 PASS All observations passed contract passed 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.

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