Records/npm/ws/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 8.21.3 FAIL
• 8.21.1 FAIL
• 8.21.0 PASS 1 passing observations
• 8.18.3 PASS 1 passing observations
• 8.18.0 PASS 3 passing observations

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-18 → 2026-08-18

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release 8.21.0 → first failing release 8.21.1

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

Evidence gaps

• The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
• No resolved dependency tree for 8.21.0 or for 8.21.1, so the versions either side of the boundary could not be compared.
• No failure domain was inferred for this failure.

Published answers for the affected releases

• ws 8.21.3: WebSocketServer Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWws.WebSocketServer MIT-0 · 2026-08-23
• ws 8.21.3 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-23
• ws 8.21.3: Why socket.io-client cannot talk to a plain WebSocket server due to Engine.IO handshake and Socket.IO wire framing Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWioWebSocketServernode MIT-0 · 2026-08-16
• ws 8.21.1: WebSocket.createWebSocketStream Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWWebSocket.createWebSocketStreamnode 22.23.2 MIT-0 · 2026-09-01
• ws 8.21.1: WebSocketServer.handleUpgrade Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWWebSocketServer.handleUpgrade MIT-0 · 2026-08-30
• ws 8.21.1: Route multiple WebSocket endpoints on a single HTTP server using WebSocketServer noServer and handleUpgrade Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWWebSocketServerWebSocketServer.prototype.handleUpgradenode 22 MIT-0 · 2026-08-28