Recordsnpmesquery
Change the conditions
Current conditions
esquery @1.7.0alpine musl · x64 · node 22 · npm · node
3 of 3 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 (3)
- Project observations
- 4 / 4
- Contract verifications
- 3 / 3
- Usage records
- 3
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
3 of 3 passed
Verified — this network ran a contract at this coordinate.
-
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.7.0
windows · node@24.13 · moduleSystem=esm · executionContext=node
32 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
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 | 1.7.0 | 1.6.0 |
|---|---|---|
| estraverse | 5.3.0 | 5.3.0 |
Moved: 0 · 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.