Recordsnpm@isaacs/brace-expansion5.0.1
Change the conditions
Current conditions
@isaacs/brace-expansion @5.0.1windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
11 of 11 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 (6)
- Project observations
- 11 / 11
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-18
Dependency Health
Observed combinations and failure evidence for this release
First observed break
5.0.1
linux · node@22.23 · executionContext=node · moduleSystem=cjs
14 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @isaacs/balanced-match | 4.0.1 | PASS All observations passed | contract passed | 14 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.1 | 5.0.0 |
|---|---|---|
| @isaacs/balanced-match | 4.0.1 | 4.0.1 |
Moved: 0 · 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.