Recordsnpm@eslint/config-array0.19.2
Change the conditions
Current conditions
@eslint/config-array @0.19.2windows 11 · x64 · node 24 · npm 11 · node
package-level total, not an API
2 of 2 passed
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (2)
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-17
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.19.2
linux · node@22.23 · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:d479d1ac8b042f76ae5ec1fb49e53b5ae3b6fe2e6258b4879b585a3a55ea72c3
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @eslint/object-schema | 2.1.7 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| minimatch | 3.1.5 | CANDIDATE Correlated change; unproven combination | contract passed | 5 project-days |
| debug | 4.4.3 | PASS All observations passed | contract passed | 5 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 | 0.23.5 | 0.21.2 | 0.19.2 |
|---|---|---|---|
| @eslint/object-schema | 3.0.5 | 2.1.7 | 2.1.7 |
| minimatch | 10.2.6 | 3.1.5 | 3.1.5 |
| debug | 4.4.3 | 4.4.3 | 4.4.3 |
Moved: 2 · 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.