Recordsnpmp-limit2.3.0
Change the conditions
Current conditions
p-limit @2.3.0windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
13 of 18 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (2)
- Project observations
- 13 / 18
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 5
- Last recorded
- 2026-08-17
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| 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.
| Library | 3.1.0 | 2.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
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×14 2.3.0 → 3.1.0 → 7.3.1 executionContext=node · moduleSystem=cjsEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-13 · Last seen: 2026-08-29Diagnostic re-verification candidate