CodeSampleX

Recordsnpmsocks2.8.7SocksClient

Change the conditions
Fixed
SymbolSocksClient Package managernpm
Filter OSdebian glibc Runtimenode 22 Package version2.8.7 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

SocksClient @2.8.7debian 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 (2)

Project observations
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

2.8.7

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:eaedb90db10c0c5ab933e412e46de0e8e50b5dbc7c05eeb586cf7a49f2b55cc4

View exact conditions View failure cluster
Library Version Health Measured there Projects
ip-address 10.1.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
ip-address 10.7.4 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
smart-buffer 4.2.0 PASS All observations passed contract passed 9 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.

Library2.8.102.8.92.8.7
ip-address 10.7.0 10.3.1 10.1.0
smart-buffer 4.2.0 4.2.0 4.2.0

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