CodeSampleX

Recordsnpmhosted-git-info4.1.0

Change the conditions
Fixed
OSalpine musl Architecturex64
Filter Runtimenode 22 Package version4.1.0 Symbolwhole package Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

hosted-git-info @4.1.0alpine musl · x64 · node 22 · npm · node

package-level total, not an API

1 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 came back clean (1)

Project observations
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-05
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

4.1.0

windows · node@24.13 · moduleSystem=esm · executionContext=node

31 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
lru-cache 6.0.0 CANDIDATE Correlated change; unproven combination contract passed 23 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