CodeSampleX

Recordsnpm@npmcli/agent4.0.0

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

Current conditions

@npmcli/agent @4.0.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

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Steady 4

Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
lru-cache 11.2.4 CHANGED Version changed, no linked failure contract passed 1 project-day
agent-base 7.1.4 PASS All observations passed contract passed 1 project-day
http-proxy-agent 7.0.2 PASS All observations passed contract passed 1 project-day
https-proxy-agent 7.0.6 PASS All observations passed contract passed 1 project-day
socks-proxy-agent 8.0.5 PASS All observations passed contract passed 1 project-day

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.

Moved: 1 · unchanged at every release: 4

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.