Recordsnpmsocks-proxy-agent8.0.5
Change the conditions
Current conditions
socks-proxy-agent @8.0.5debian glibc · x64 · node 22 · npm · chrome 134
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (3)
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-07
Dependency Health
Observed combinations and failure evidence for this release
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.