Recordsnpmwhich
Change the conditions
Current conditions
which @2.0.2ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 97 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
- 316 / 327
- Contract verifications
- 0 / 97
- Usage records
- 226
- Independent reporting peers
- 3
- Failures with a captured fingerprint
- 10 / 11
- Last recorded
- 2026-10-21
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 97 passed
Verified — this network ran a contract at this coordinate.
-
which.sync
3 of 3 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.0.2
windows · node@24.13 · moduleSystem=esm · executionContext=node
96 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| isexe | 2.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 280 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.