CodeSampleX

Recordsnpmbrowserslist4.28.8browserslist.coverage

Change the conditions
Fixed
OSwindows 11 Symbolbrowserslist.coverage Execution contextnode
Filter Runtimenode 24 Package version4.28.8 Architecturex64 Package managernpm 11 Clear filters

Current conditions

browserslist.coverage @4.28.8windows 11 · x64 · node 24 · npm 11 · node

2 of 2 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
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 23 · Steady 0

First observed break

4.28.8

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

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

Library Version Health Measured there Projects
baseline-browser-mapping 2.11.15 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
baseline-browser-mapping 2.11.16 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
baseline-browser-mapping 2.11.18 CANDIDATE Correlated change; unproven combination contract passed 15 project-days
baseline-browser-mapping 2.11.19 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
baseline-browser-mapping 2.11.20 CANDIDATE Correlated change; unproven combination contract passed 78 project-days
baseline-browser-mapping 2.11.21 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
caniuse-lite 1.0.30001809 CANDIDATE Correlated change; unproven combination contract passed 29 project-days
caniuse-lite 1.0.30001810 CANDIDATE Correlated change; unproven combination contract passed 101 project-days
electron-to-chromium 1.5.411 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
electron-to-chromium 1.5.412 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
electron-to-chromium 1.5.414 CANDIDATE Correlated change; unproven combination builds observed 1 project-day
electron-to-chromium 1.5.415 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
electron-to-chromium 1.5.416 CANDIDATE Correlated change; unproven combination builds observed 3 project-days
electron-to-chromium 1.5.418 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
electron-to-chromium 1.5.419 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
electron-to-chromium 1.5.420 CANDIDATE Correlated change; unproven combination contract passed 60 project-days
electron-to-chromium 1.5.421 CANDIDATE Correlated change; unproven combination contract passed 12 project-days
electron-to-chromium 1.5.422 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
node-releases 2.0.53 CANDIDATE Correlated change; unproven combination contract passed 30 project-days
node-releases 2.0.54 CANDIDATE Correlated change; unproven combination contract passed 96 project-days
update-browserslist-db 1.3.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
update-browserslist-db 1.3.1 CANDIDATE Correlated change; unproven combination contract passed 30 project-days
update-browserslist-db 1.3.2 CANDIDATE Correlated change; unproven combination contract passed 95 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: 5 · 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.

Recent failure clusters

Showing the 12 most-reported of 225 recorded failure clusters. The rest are single reports.