Recordsnpm@babel/core
Change the conditions
Current conditions
@babel/core @7.26.0debian glibc · x64 · node 22 · npm · node
9 of 9 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 (9)
- Project observations
- 12 / 12
- Contract verifications
- 9 / 9
- Usage records
- 6
- Independent reporting peers
- 1
- Last recorded
- 2026-09-16
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
9 of 9 passed
Verified — this network ran a contract at this coordinate.
-
@babel/core.transformFileAsync
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
7.26.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
5 FAIL
· stage: UNKNOWN
· fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/code-frame | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/generator | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/helper-compilation-targets | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/helper-module-transforms | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/helpers | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/parser | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/template | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/traverse | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/types | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| convert-source-map | 2.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| semver | 6.3.1 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @ampproject/remapping | 2.3.0 | PASS All observations passed | contract passed | 19 project-days |
| debug | 4.4.3 | PASS All observations passed | contract passed | 19 project-days |
| gensync | 1.0.0-beta.2 | PASS All observations passed | contract passed | 19 project-days |
| json5 | 2.2.3 | PASS All observations passed | contract passed | 19 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.