CodeSampleX

Recordsnpm@types/babel__template7.4.4

Change the conditions
Fixed
Runtimenode 22 Package managernpm 11
Filter OSwindows 11 Package version7.4.4 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

@types/babel__template @7.4.4windows 11 · x64 · node 22 · npm 11 · node

package-level total, not an API

10 of 11 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 (1)

Project observations
10 / 11
Contract verifications
nothing at this coordinate
Usage records
5
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-24
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 4

First observed break

7.4.4

windows · node@24.13 · moduleSystem=esm · executionContext=node

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

View exact conditions View failure cluster
Library Version Health Measured there Projects
@babel/parser 7.29.7 PASS All observations passed contract passed 3 project-days
@babel/parser 7.29.8 PASS All observations passed contract passed 21 project-days
@babel/types 7.29.7 PASS All observations passed contract passed 3 project-days
@babel/types 7.29.8 PASS All observations passed contract passed 21 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.

Recent failure clusters