CodeSampleX

Recordsnpmsocks-proxy-agent

Change the conditions
Fixed
Package version8.0.5 SymbolSocksProxyAgent
Filter Runtimenode 22 Architecturex64 Execution contextnode Clear filters

Current conditions

SocksProxyAgent @8.0.5x64 · node 22 · node

1 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and this coordinate records both a passing and a failing run of it (2)

Project observations
4 / 4
Contract verifications
1 / 2
Independent reporting peers
1
Last recorded
2026-08-30

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 1

First observed break

8.0.5

moduleSystem=esm · executionContext=node

6 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
agent-base 7.1.4 CANDIDATE Correlated change; unproven combination contract passed 70 project-days
socks 2.8.10 CANDIDATE Correlated change; unproven combination contract passed 52 project-days
socks 2.8.7 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
socks 2.8.9 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
debug 4.4.3 PASS All observations passed contract passed 71 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: 2 · 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.