Recordsnpmminimatch
Change the conditions
Current conditions
minimatch.defaults @10.1.1musl · x64 · node
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
- 3 / 3
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-28
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
windows 11 · x64 · node 24 · npm 11 · node
3 of 3 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
3.1.5
windows · node@24.13 · executionContext=node · moduleSystem=esm
128 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
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 | 10.2.6 | 10.2.5 | 10.1.1 | 9.0.9 | 9.0.5 | 5.1.9 | 3.1.5 | 3.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.