CodeSampleX

Recordsnpmbrace-expansion5.0.8

Change the conditions
Fixed
Runtimenode 24 Package version5.0.8
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

brace-expansion @5.0.8windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 40 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (1)

Project observations
47 / 56
Contract verifications
0 / 40
Usage records
216
Independent reporting peers
1
Failures with a captured fingerprint
7 / 9
Last recorded
2026-09-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

5.0.8

windows · executionContext=node

15 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
balanced-match 4.0.4 CANDIDATE Correlated change; unproven combination contract passed 6 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.125.0.95.0.82.1.72.1.42.1.32.0.21.1.211.1.181.1.171.1.12
balanced-match 4.0.4 4.0.4 4.0.4 1.0.2 1.0.2 1.0.2 1.0.2 1.0.2 1.0.2 1.0.2 1.0.2
concat-map — — — — — — — 0.0.1 0.0.1 0.0.1 0.0.1

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

Showing the 12 most-reported of 41 recorded failure clusters. The rest are single reports.