CodeSampleX

Recordsnpmminimatch9.0.9

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

Current conditions

minimatch @9.0.9ubuntu 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 (1)

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

9.0.9

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

128 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
brace-expansion 2.0.2 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
brace-expansion 2.1.3 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
brace-expansion 2.1.4 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
brace-expansion 2.1.7 CANDIDATE Correlated change; unproven combination contract passed 43 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.

Library10.2.610.2.510.1.19.0.99.0.55.1.93.1.53.1.2
brace-expansion 5.0.8 5.0.9 — 2.0.2 2.0.2 2.1.7 1.1.21 1.1.12
@isaacs/brace-expansion — — 5.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