CodeSampleX

Recordsnpm@types/yauzl2.10.3

Change the conditions
Fixed
Execution contextchrome 134
Filter OSdebian glibc Runtimenode 22 Package version2.10.3 Symbolwhole package Architecturex64 Package managernpm libcglibc Clear filters

Current conditions

@types/yauzl @2.10.3debian glibc · x64 · node 22 · npm · chrome 134

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

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
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 5

First observed break

2.10.3

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
@types/node 20.19.43 PASS All observations passed contract passed 5 project-days
@types/node 22.20.1 PASS All observations passed contract passed 9 project-days
@types/node 26.2.0 PASS All observations passed contract passed 9 project-days
@types/node 26.4.0 PASS All observations passed contract passed 4 project-days
@types/node 26.4.1 PASS All observations passed contract passed 4 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.