CodeSampleX

Recordsnpmbrace-expansion2.1.4

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

Current conditions

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

package-level total, not an API

2 of 2 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
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

2.1.4

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

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

Library Version Health Measured there Projects
balanced-match 1.0.2 CANDIDATE Correlated change; unproven combination contract passed 25 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 235 recorded failure clusters. The rest are single reports.