Recordsnpm@babel/core
Change the conditions
Current conditions
@babel/core.template @8.0.1x64 · 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 (1)
- Project observations
- 3 / 3
- 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
3 of 3 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.0.1
linux · node@22.23 · moduleSystem=esm · executionContext=node
2 FAIL
· stage: UNKNOWN
· fingerprint: sha256:455451e1a14e249427c2bc1772777b41d7ea0e8c07e3fe88a46ec6adb3bc054e
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/code-frame | 8.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 26 project-days |
| @babel/generator | 8.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 26 project-days |
| @babel/helper-compilation-targets | 8.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 23 project-days |
| @babel/helpers | 8.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 23 project-days |
| @babel/parser | 8.0.4 | CANDIDATE Correlated change; unproven combination | contract passed | 23 project-days |
| @babel/template | 8.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 23 project-days |
| @babel/traverse | 8.0.4 | CANDIDATE Correlated change; unproven combination | contract passed | 23 project-days |
| @babel/types | 8.0.4 | CANDIDATE Correlated change; unproven combination | contract passed | 23 project-days |
| convert-source-map | 2.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 25 project-days |
| semver | 7.8.5 | CANDIDATE Correlated change; unproven combination | contract passed | 23 project-days |
| @types/gensync | 1.0.5 | PASS All observations passed | contract passed | 23 project-days |
| empathic | 2.0.1 | PASS All observations passed | contract passed | 23 project-days |
| gensync | 1.0.0-beta.2 | PASS All observations passed | contract passed | 25 project-days |
| import-meta-resolve | 4.2.0 | PASS All observations passed | contract passed | 23 project-days |
| json5 | 2.2.3 | PASS All observations passed | contract passed | 25 project-days |
| obug | 2.1.4 | PASS All observations passed | contract passed | 23 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.
Moved: 11 · unchanged at every release: 12
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.