CodeSampleX

Recordsnpmreact18.3.1React.forwardRef

Change the conditions
Fixed
SymbolReact.forwardRef
Filter OSalpine musl Runtimenode 22 Package version18.3.1 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

React.forwardRef @18.3.1alpine musl · 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 (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-26

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

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.

Library18.3.118.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.

Recent failure clusters