CodeSampleX

Recordsnpmpac-proxy-agent7.2.0PacProxyAgent

Change the conditions
Fixed
OSalpine musl SymbolPacProxyAgent Execution contextnode
Filter Runtimenode 22 Package version7.2.0 Architecturex64 Package managernpm libcmusl Clear filters

Current conditions

PacProxyAgent @7.2.0alpine 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 (2)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 8

First observed break

7.2.0

executionContext=node

9 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
@tootallnate/quickjs-emscripten 0.23.0 PASS All observations passed contract passed 15 project-days
agent-base 7.1.4 PASS All observations passed contract passed 15 project-days
debug 4.4.3 PASS All observations passed contract passed 15 project-days
get-uri 6.0.5 PASS All observations passed contract passed 14 project-days
http-proxy-agent 7.0.2 PASS All observations passed contract passed 14 project-days
https-proxy-agent 7.0.6 PASS All observations passed contract passed 14 project-days
pac-resolver 7.0.1 PASS All observations passed contract passed 13 project-days
socks-proxy-agent 8.0.5 PASS All observations passed contract passed 13 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.

Recent failure clusters