Recordsnpmenhanced-resolve
Change the conditions
Current conditions
enhanced-resolve @5.24.5debian glibc · x64 · node 22 · npm · node
2 of 2 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (2)
- Project observations
- 8 / 8
- Contract verifications
- 2 / 2
- Usage records
- 5
- Independent reporting peers
- 1
- Last recorded
- 2026-10-10
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
2 of 2 passed
Verified — this network ran a contract at this coordinate.
-
enhanced-resolve.create
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 1. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| tapable | 2.3.3 | CHANGED Version changed, no linked failure | contract passed | 8 project-days |
| graceful-fs | 4.2.11 | PASS All observations passed | contract passed | 8 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: 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.