CodeSampleX

Recordsnpmlocate-path5.0.0locatePath.sync

Change the conditions
Fixed
Package version5.0.0 SymbollocatePath.sync
Filter OSalpine musl Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

locatePath.sync @5.0.0alpine musl · x64 · node 22 · npm · node

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
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-27
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

5.0.0

linux · node@22.23 · executionContext=node

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
p-locate 4.1.0 CANDIDATE Correlated change; unproven combination contract passed 16 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.

Library6.0.05.0.02.0.0
p-locate 5.0.0 4.1.0 2.0.0
path-exists — — 3.0.0

Moved: 1 · unchanged at every release: 1

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