Recordsnpmregexpu-core6.4.0
Change the conditions
Current conditions
regexpu-core @6.4.0windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
3 of 7 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 (2)
- Project observations
- 3 / 7
- Contract verifications
- nothing at this coordinate
- Usage records
- 2
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 4
- Last recorded
- 2026-08-17
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Steady 6
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.
Recent failure clusters
-
observed PROJECT_TEST ERR_ASSERTION Evidence gap ×4 6.4.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-17 · Last seen: 2026-08-17Diagnostic re-verification candidate