Recordsnpm@eslint/eslintrc3.3.6
Change the conditions
Current conditions
@eslint/eslintrc @3.3.6windows 11 · x64 · node (version not recorded) · pnpm 10 · node
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (5)
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-01
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
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| ajv | 6.15.0 | CANDIDATE Correlated change; unproven combination | contract passed | 17 project-days |
| espree | 10.4.0 | CANDIDATE Correlated change; unproven combination | contract passed | 17 project-days |
| globals | 14.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 17 project-days |
| js-yaml | 4.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| js-yaml | 4.3.1 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| js-yaml | 4.3.2 | CANDIDATE Correlated change; unproven combination | contract passed | 10 project-days |
| minimatch | 3.1.5 | CANDIDATE Correlated change; unproven combination | contract passed | 17 project-days |
| debug | 4.4.3 | PASS All observations passed | contract passed | 17 project-days |
| ignore | 5.3.2 | PASS All observations passed | contract passed | 17 project-days |
| import-fresh | 3.3.1 | PASS All observations passed | contract passed | 17 project-days |
| strip-json-comments | 3.1.1 | PASS All observations passed | contract passed | 16 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 | 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.
Recent failure clusters
-
observed PROCESS_START process start failed Evidence gap ×4 3.3.6 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-09-02 · Last seen: 2026-09-16Diagnostic re-verification candidate