CodeSampleX

Recordsnpmlocate-path2.0.0

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

Current conditions

locate-path @2.0.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

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
2 / 2
Contract verifications
0 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-14
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

2.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 2.0.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
path-exists 3.0.0 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.

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