Recordsnpm@babel/types8.0.0
Change the conditions
Current conditions
@babel/types @8.0.0alpine musl · x64 · node 22 · npm · node
package-level total, not an API
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
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/helper-string-parser | 8.0.0 | CHANGED Version changed, no linked failure | contract passed | 2 project-days |
| @babel/helper-validator-identifier | 8.0.4 | CHANGED Version changed, no linked failure | contract passed | 2 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 | 8.0.0 | 7.29.8 | 7.29.7 | 7.28.5 |
|---|---|---|---|---|---|
| @babel/helper-string-parser | 8.0.0 | 8.0.0 | 7.29.7 | 7.29.7 | 7.27.1 |
| @babel/helper-validator-identifier | 8.0.4 | 8.0.4 | 7.29.7 | 7.29.7 | 7.28.5 |
Moved: 2 · unchanged at every release: 0
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.