CodeSampleX

Recordsnpmpath-scurry1.11.1

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

Current conditions

path-scurry @1.11.1ubuntu 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
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

1.11.1

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

4 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

View exact conditions View failure cluster
Library Version Health Measured there Projects
lru-cache 10.4.3 CANDIDATE Correlated change; unproven combination contract passed 65 project-days
minipass 7.1.2 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
minipass 7.1.3 CANDIDATE Correlated change; unproven combination contract passed 64 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.

Library2.0.22.0.11.11.1
lru-cache 11.5.1 11.2.4 10.4.3
minipass 7.1.3 7.1.2 7.1.2

Moved: 2 · 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