CodeSampleX

Recordsnpmpac-proxy-agent7.2.0

Change the conditions
Fixed
Runtimenode 24 Package version7.2.0
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

pac-proxy-agent @7.2.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

18 of 23 passed

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
18 / 23
Contract verifications
nothing at this coordinate
Usage records
3
Independent reporting peers
1
Failures with a captured fingerprint
0 / 5
Last recorded
2026-08-18
Evidence you can open

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

View exact conditions View failure cluster
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