CodeSampleX

Recordsnpmhosted-git-info9.0.3

Change the conditions
Fixed
Runtimenode 22 Package version9.0.3 Package manageryarn 4
Filter OSubuntu glibc Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

hosted-git-info @9.0.3ubuntu glibc · x64 · node 22 · yarn 4 · node

package-level total, not an API

3 of 3 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
3 / 3
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-07

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

9.0.3

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

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

Library Version Health Measured there Projects
lru-cache 11.5.1 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
lru-cache 11.5.2 CANDIDATE Correlated change; unproven combination 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.0.39.0.28.1.07.0.24.1.0
lru-cache 11.5.2 11.2.4 10.4.3 10.4.3 6.0.0

Moved: 1 · unchanged at every release: 0

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