Recordsnpmhttp-proxy-agent7.0.2
Change the conditions
Current conditions
http-proxy-agent @7.0.2debian glibc · x64 · node 22 · npm · chrome 134
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.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-07
Dependency Health
Observed combinations and failure evidence for this release
First observed break
7.0.2
windows · node@24.13 · moduleSystem=esm · executionContext=node
31 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| agent-base | 7.1.4 | CANDIDATE Correlated change; unproven combination | contract passed | 56 project-days |
| debug | 4.4.3 | PASS All observations passed | contract passed | 60 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.
| Library | 9.1.0 | 7.0.2 | 5.0.0 |
|---|---|---|---|
| agent-base | 9.0.0 | 7.1.4 | 6.0.2 |
| @tootallnate/once | — | — | 2.0.1 |
| debug | 4.4.3 | 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.