CodeSampleX

Recordsnpmsocks2.8.9SocksClient.createConnection

Change the conditions
Fixed
Package version2.8.9 SymbolSocksClient.createConnection
Filter OSalpine musl Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

SocksClient.createConnection @2.8.9alpine musl · 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 (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-23

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

2.8.9

linux · node@22.23 · executionContext=node · moduleSystem=cjs

15 FAIL · stage: UNKNOWN · fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868

Library Version Health Measured there Projects
ip-address 10.3.1 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
ip-address 10.5.0 CANDIDATE Correlated change; unproven combination contract passed 19 project-days
smart-buffer 4.2.0 PASS All observations passed contract passed 21 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

Showing the 12 most-reported of 25 recorded failure clusters. The rest are single reports.