Recordsnpmengine.io-client
Change the conditions
Current conditions
WebSocket @6.6.6x64 · node 22 · 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
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-27
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
1 of 1 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
6.6.6
linux · node@22.23 · moduleSystem=cjs · executionContext=node
10 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @socket.io/component-emitter | 3.1.2 | PASS All observations passed | contract passed | 8 project-days |
| debug | 4.4.3 | PASS All observations passed | contract passed | 7 project-days |
| engine.io-parser | 5.2.3 | PASS All observations passed | contract passed | 7 project-days |
| ws | 8.21.3 | PASS All observations passed | contract passed | 7 project-days |
| xmlhttprequest-ssl | 2.1.2 | PASS All observations passed | contract passed | 6 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.