CodeSampleX

Recordsnpm@npmcli/agent3.0.0@npmcli/agent.cache

Change the conditions
Fixed
OSubuntu glibc Symbol@npmcli/agent.cache
Filter Runtimenode 22 Package version3.0.0 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@npmcli/agent.cache @3.0.0ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
nothing at this coordinate
Contract verifications
0 / 1
Last recorded
2026-10-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 4

First observed break

3.0.0

linux · node@22.23 · moduleSystem=esm · executionContext=node

2 FAIL · stage: UNKNOWN · fingerprint: sha256:536db39a2e089f7ed603954e4a67695a077090ed80e3d0d1ef21bd2d6a9e9b21

Library Version Health Measured there Projects
lru-cache 10.4.3 CANDIDATE Correlated change; unproven combination contract passed 54 project-days
agent-base 7.1.4 PASS All observations passed contract passed 54 project-days
http-proxy-agent 7.0.2 PASS All observations passed contract passed 54 project-days
https-proxy-agent 7.0.6 PASS All observations passed contract passed 54 project-days
socks-proxy-agent 8.0.5 PASS All observations passed contract passed 54 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.

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.

Recent failure clusters