Recordsnpm@eslint/core0.11.0
Change the conditions
Current conditions
@eslint/core @0.11.0alpine musl · x64 · node 22 · npm · node
package-level total, not an API
1 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 came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
All 1 dependencies report steady passing evidence.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @types/json-schema | 7.0.15 | PASS All observations passed | contract passed | 3 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 | 1.2.1 | 0.17.0 | 0.13.0 | 0.11.0 |
|---|---|---|---|---|
| @types/json-schema | 7.0.15 | 7.0.15 | 7.0.15 | 7.0.15 |
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.