Recordsnpm@babel/traverse
Change the conditions
Current conditions
@babel/traverse @7.29.7ubuntu glibc · x64 · node 22 · npm 10 · node
3 of 3 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 (2)
- Project observations
- 3 / 3
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-09-05
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
3 of 3 passed
Observed — real project builds reported from this coordinate.
-
@babel/traverse.default
2 of 2 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
7.29.7
windows · executionContext=node
5 FAIL · stage: PROJECT_TEST
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/code-frame | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| @babel/generator | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| @babel/generator | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| @babel/helper-globals | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| @babel/parser | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 4 project-days |
| @babel/parser | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| @babel/template | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 7 project-days |
| @babel/types | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| @babel/types | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 3 project-days |
| debug | 4.4.3 | PASS All observations passed | 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 | 8.0.4 | 7.29.8 | 7.29.7 | 7.28.5 |
|---|---|---|---|---|
| @babel/code-frame | 8.0.0 | 7.29.7 | 7.29.7 | 7.27.1 |
| @babel/generator | 8.0.0 | 7.29.8 | 7.29.8 | 7.28.5 |
| @babel/helper-globals | 8.0.0 | 7.29.7 | 7.29.7 | 7.28.0 |
| @babel/parser | 8.0.4 | 7.29.8 | 7.29.8 | 7.28.5 |
| @babel/template | 8.0.0 | 7.29.7 | 7.29.7 | 7.27.2 |
| @babel/types | 8.0.4 | 7.29.8 | 7.29.8 | 7.28.5 |
| debug | — | 4.4.3 | 4.4.3 | 4.4.3 |
| obug | 2.1.4 | — | — | — |
Moved: 6 · 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.