CodeSampleX

Recordsnpm@npmcli/map-workspaces4.0.2

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

Current conditions

@npmcli/map-workspaces @4.0.2ubuntu 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.

there is a sample here, and nothing of ours has run it at this coordinate yet (2)

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 4 · Steady 0

First observed break

4.0.2

linux · node@22.23 · executionContext=node

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
@npmcli/name-from-folder 3.0.0 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
@npmcli/package-json 6.2.0 CANDIDATE Correlated change; unproven combination contract passed 18 project-days
glob 10.5.0 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
minimatch 9.0.9 CANDIDATE Correlated change; unproven combination contract passed 18 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.34.0.2
@npmcli/name-from-folder 4.0.0 3.0.0
@npmcli/package-json 7.0.4 6.2.0
glob 13.0.0 10.5.0
minimatch 10.1.1 9.0.9

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