CodeSampleX

Recordsnpmp-limit2.3.0

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

Current conditions

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

package-level total, not an API

0 of 10 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
37 / 37
Contract verifications
0 / 10
Usage records
7
Independent reporting peers
3
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
p-try 2.2.0 contract passed 10 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.

Library3.1.02.3.0
p-try 2.2.0
yocto-queue 0.1.0

Moved: 0 · unchanged at every release: 2

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