Recordsnpmbrace-expansion2.1.3
Change the conditions
Current conditions
brace-expansion @2.1.3alpine musl · x64 · node 22 · npm · node
package-level total, not an API
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.1.3
windows · executionContext=node
15 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| balanced-match | 1.0.2 | 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.
| Library | 5.0.12 | 5.0.9 | 5.0.8 | 2.1.7 | 2.1.4 | 2.1.3 | 2.0.2 | 1.1.21 | 1.1.18 | 1.1.17 | 1.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.