CodeSampleX

Recordsnpmhttp-proxy-agent5.0.0

Change the conditions
Fixed
Package version5.0.0 Architecturex64 libcmusl
Filter OSalpine musl Runtimenode 22 Symbolwhole package Package managernpm Execution contextnode Clear filters

Current conditions

http-proxy-agent @5.0.0alpine musl · x64 · node 22 · npm · node

package-level total, not an API

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
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-30

Dependencies

LibraryVersionMeasured thereProjects
@tootallnate/once 2.0.1 contract passed 3 project-days
agent-base 6.0.2 contract passed 3 project-days
debug 4.4.3 contract passed 3 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.

Library7.0.25.0.0
agent-base 7.1.4 6.0.2
@tootallnate/once 2.0.1
debug 4.4.3 4.4.3

Moved: 1 · unchanged at every release: 2

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 19 recorded failure clusters. The rest are single reports.