Recordsnpmreact
Change the conditions
Current conditions
react @18.3.1windows 11 · x64 · node 24 · npm 11 · node
0 of 20 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (17)
- Project observations
- 52 / 103
- Contract verifications
- 0 / 20
- Usage records
- 91
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 49 / 51
- Last recorded
- 2026-09-16
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 20 passed
Verified — this network ran a contract at this coordinate.
-
react.CSSProperties
0 of 11 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
18.3.1
windows · executionContext=node
11 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| loose-envify | 1.4.0 | PASS All observations passed | contract passed | 17 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 | 18.3.1 | 18.2.0 |
|---|---|---|
| loose-envify | 1.4.0 | 1.4.0 |
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.