CodeSampleX

Recordsnpmhttps-proxy-agent9.1.0

Change the conditions
Fixed
Package version9.1.0 Architecturex64 Package managernpm
Filter OSdebian glibc Runtimenode 22 Symbolwhole package Execution contextnode libcglibc Clear filters

Current conditions

https-proxy-agent @9.1.0debian glibc · x64 · node 22 · npm · node

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.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-14
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

9.1.0

linux · node@22.23 · executionContext=node

4 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

View exact conditions View failure cluster
Library Version Health Measured there Projects
agent-base 9.0.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
debug 4.4.3 PASS All observations passed contract passed 2 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