CodeSampleX

Recordsnpmfind-up2.1.0

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

Current conditions

find-up @2.1.0ubuntu glibc · x64 · node 22 · yarn 4 · node

package-level total, not an API

4 of 4 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
4 / 4
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

2.1.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
locate-path 2.0.0 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.

Library5.0.04.1.02.1.0
locate-path 6.0.0 5.0.0 2.0.0
path-exists 4.0.0 4.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