Recordsnpmp-locate2.0.0
Change the conditions
Current conditions
p-locate @2.0.0ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 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 failed
- Project observations
- 2 / 2
- Contract verifications
- 0 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.0.0
linux · node@22.23 · executionContext=node
8 FAIL
· stage: UNKNOWN
· fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| p-limit | 1.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 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.
Moved: 1 · unchanged at every release: 0
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 UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×8 2.0.0 → 4.1.0 → 5.0.0 executionContext=node · os=linux · runtime=node@22.23 sha256:986d98189e70…node:internal/modules/run_main:<n> · triggerUncaughtException( · ^ · AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 2 · First recorded: 2026-08-29 · Last seen: 2026-09-14Diagnostic re-verification candidate