Recordsnpmespree10.4.0
Change the conditions
Current conditions
espree @10.4.0windows 11 · x64 · node 22 · pnpm 10 · node
package-level total, not an API
11 of 14 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 (3)
- Project observations
- 11 / 14
- Contract verifications
- nothing at this coordinate
- Usage records
- 72
- Independent reporting peers
- 1
- Failures with a captured fingerprint
- 0 / 3
- Last recorded
- 2026-08-24
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| acorn | 8.18.0 | contract passed | 5 project-days |
| acorn-jsx | 5.3.2 | contract passed | 5 project-days |
| eslint-visitor-keys | 4.2.1 | 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 | 11.2.0 | 10.4.0 |
|---|---|---|
| eslint-visitor-keys | 5.0.1 | 4.2.1 |
| acorn | 8.18.0 | 8.18.0 |
| acorn-jsx | 5.3.2 | 5.3.2 |
Moved: 1 · unchanged at every release: 2
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 PROJECT_TEST Evidence gap ×5 10.4.0 executionContext=node · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-21 · Last seen: 2026-08-25Diagnostic re-verification candidate