Recordsnpmregexpu-core
Change the conditions
Current conditions
regexpu-core @6.4.0debian glibc · x64 · node 22 · npm · 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 (2)
- Project observations
- 4 / 4
- Contract verifications
- 1 / 1
- Usage records
- 5
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
regexpu-core.default
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
6.4.0
windows · node@24.13 · moduleSystem=esm · executionContext=node
4 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| regenerate | 1.4.2 | PASS All observations passed | contract passed | 39 project-days |
| regenerate-unicode-properties | 10.2.2 | PASS All observations passed | contract passed | 39 project-days |
| regjsgen | 0.8.0 | PASS All observations passed | contract passed | 38 project-days |
| regjsparser | 0.13.2 | PASS All observations passed | contract passed | 38 project-days |
| unicode-match-property-ecmascript | 2.0.0 | PASS All observations passed | contract passed | 38 project-days |
| unicode-match-property-value-ecmascript | 2.2.1 | PASS All observations passed | contract passed | 38 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.