Recordsnpm@eslint/eslintrc
Change the conditions
Current conditions
FlatCompat @3.3.6x64 · node 22 · node
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 (2)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-20
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
1 of 1 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
3.3.6
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 | 3.3.7 | 3.3.6 | 2.1.4 |
|---|---|---|---|
| ajv | 6.15.0 | 6.15.0 | 6.12.6 |
| espree | 10.4.0 | 10.4.0 | 9.6.1 |
| globals | 14.0.0 | 14.0.0 | 13.24.0 |
| js-yaml | 4.3.2 | 4.3.0 | 4.1.1 |
| minimatch | 3.1.5 | 3.1.5 | 3.1.2 |
| debug | 4.4.3 | 4.4.3 | 4.4.3 |
| ignore | 5.3.2 | 5.3.2 | 5.3.2 |
| import-fresh | 3.3.1 | 3.3.1 | 3.3.1 |
| strip-json-comments | 3.1.1 | 3.1.1 | 3.1.1 |
Moved: 5 · unchanged at every release: 4
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.