Recordsnpmws8.18.0WebSocketServer
shared with 2 packages — this evidence cannot say whose API it is
Published samples
- ws 8.18.0: Prove that WebSocketServer in noServer mode requires an explicit callback to emit the connection event and enforces mutually exclusive server binding options 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.handleUpgradeWebSocketServer.prototype.shouldHandlenode MIT-0 · 2026-08-17
- ws 8.18.0: Prove that WebSocket.Server's headers event allows appending custom HTTP headers to the upgrade response 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. HOWWebSocketServernode MIT-0 · 2026-08-17
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Observations: PROJECT_TEST 1✓ — Verified: CONTRACT 6✓
|
HIGH | 1 | 6 | 100% | 1 · 3✓ | 2026-09-08 |
snapshot · 2026-09-15
Failure clusters
No failure clusters observed.