Recordsnpmmicromatch
Change the conditions
Current conditions
micromatch.makeRe @4.0.8x64 · node 22 · 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
- 4 / 6
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 2
- 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.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
4 of 6 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.0.8
linux · node@22.23 · executionContext=node
7 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| braces | 3.0.3 | PASS All observations passed | contract passed | 26 project-days |
| picomatch | 2.3.1 | PASS All observations passed | contract passed | 3 project-days |
| picomatch | 2.3.2 | PASS All observations passed | contract passed | 22 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.