CodeSampleX

Recordsnpmhttps-proxy-agent7.0.6

Change the conditions
Fixed
Runtimenode 22 Package managerpnpm 10 Execution contextnode
Filter OSwindows 11 Package version7.0.6 Symbolwhole package Architecturex64 Clear filters

Current conditions

https-proxy-agent @7.0.6windows 11 · x64 · node 22 · pnpm 10 · node

package-level total, not an API

1 of 1 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 (2)

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Usage records
12
Independent reporting peers
1
Last recorded
2026-08-21
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

7.0.6

windows · node@24.13 · moduleSystem=esm · executionContext=node

31 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
agent-base 7.1.4 CANDIDATE Correlated change; unproven combination contract passed 59 project-days
debug 4.4.3 PASS All observations passed contract passed 62 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.

Library9.1.07.0.65.0.1
agent-base 9.0.0 7.1.4 6.0.2
debug 4.4.3 4.4.3 4.4.3

Moved: 1 · 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.

Recent failure clusters