CodeSampleX

Recordsnpmbrowserslist4.28.7browserslist.loadConfig

Change the conditions
Fixed
OSdebian glibc Symbolbrowserslist.loadConfig
Filter Runtimenode 22 Package version4.28.7 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

browserslist.loadConfig @4.28.7debian glibc · x64 · node 22 · npm · node

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
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 14 · Steady 0

First observed break

4.28.7

windows · executionContext=node

7 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
baseline-browser-mapping 2.11.19 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
baseline-browser-mapping 2.11.24 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
baseline-browser-mapping 2.11.7 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
caniuse-lite 1.0.30001806 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
caniuse-lite 1.0.30001810 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
electron-to-chromium 1.5.398 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
electron-to-chromium 1.5.415 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
electron-to-chromium 1.5.430 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
node-releases 2.0.51 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
node-releases 2.0.53 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
node-releases 2.0.55 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
update-browserslist-db 1.2.3 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
update-browserslist-db 1.3.1 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
update-browserslist-db 1.3.3 CANDIDATE Correlated change; unproven combination contract passed 7 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