CodeSampleX

Recordsnpmsocks2.8.10socks.SocksClient.createConnectionChain

Change the conditions
Fixed
OSdebian glibc Symbolsocks.SocksClient.createConnectionChain
Filter Runtimenode 22 Package version2.8.10 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

socks.SocksClient.createConnectionChain @2.8.10debian glibc · 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 (3)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

2.8.10

linux · node@22.23 · executionContext=node

5 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

Library Version Health Measured there Projects
ip-address 10.7.0 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
ip-address 10.7.4 CANDIDATE Correlated change; unproven combination contract passed 52 project-days
smart-buffer 4.2.0 PASS All observations passed contract passed 80 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: 1

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