CodeSampleX

Recordsnpmbrowserslist4.28.8

Change the conditions
Fixed
Runtimenode (version not recorded) Execution contextnode
Filter OSwindows 11 Package version4.28.8 Symbolwhole package Architecturex64 Package managerpnpm 10 Clear filters

Current conditions

browserslist @4.28.8windows 11 · x64 · node (version not recorded) · pnpm 10 · node

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 (3)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-01
Evidence you can open

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

View exact conditions View failure cluster
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.

Library4.29.04.28.94.28.84.28.74.28.1
baseline-browser-mapping 2.11.25 2.11.23 2.11.15 2.11.19 2.9.11
caniuse-lite 1.0.30001810 1.0.30001810 1.0.30001809 1.0.30001806 1.0.30001761
electron-to-chromium 1.5.432 1.5.427 1.5.414 1.5.415 1.5.267
node-releases 2.0.56 2.0.55 2.0.53 2.0.53 2.0.27
update-browserslist-db 1.3.3 1.2.3 1.3.0 1.3.1 1.2.3

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