CodeSampleX

Recordsnpmp-limit2.3.0

Change the conditions
Fixed
Package version2.3.0 Package managernpm 10
Filter OSubuntu glibc Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

p-limit @2.3.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 11 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (2)

Project observations
43 / 43
Contract verifications
0 / 11
Usage records
7
Independent reporting peers
3
Last recorded
2026-09-02
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

2.3.0

moduleSystem=cjs · executionContext=node

14 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
p-try 2.2.0 CANDIDATE Correlated change; unproven combination contract passed 18 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.

Library7.3.13.1.02.3.01.3.0
p-try — — 2.2.0 1.0.0
yocto-queue 1.2.2 0.1.0 — —
yoga-layout 3.2.1 — — —

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