CodeSampleX

Recordsnpmroarr2.15.4

Change the conditions
Fixed
Runtimenode (version not recorded) Package managernpm
Filter OSwindows 11 Package version2.15.4 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

roarr @2.15.4windows 11 · x64 · node (version not recorded) · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (3)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-13
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 6

First observed break

2.15.4

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

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
boolean 3.2.0 PASS All observations passed contract passed 26 project-days
detect-node 2.1.0 PASS All observations passed contract passed 19 project-days
globalthis 1.0.4 PASS All observations passed contract passed 22 project-days
json-stringify-safe 5.0.1 PASS All observations passed contract passed 20 project-days
semver-compare 1.0.0 PASS All observations passed contract passed 19 project-days
sprintf-js 1.1.3 PASS All observations passed contract passed 19 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