CodeSampleX

Recordsnpmnpm-run-path4.0.1npmRunPath.env

Change the conditions
Fixed
Package version4.0.1 SymbolnpmRunPath.env
Filter OSalpine musl Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

npmRunPath.env @4.0.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 (2)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-27
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

4.0.1

windows · node@24.13 · moduleSystem=cjs · executionContext=node

5 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
path-key 3.1.1 CANDIDATE Correlated change; unproven combination contract passed 12 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.

Library6.0.05.3.04.0.1
path-key 4.0.0 4.0.0 3.1.1
unicorn-magic 0.3.0 — —

Moved: 1 · 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