CodeSampleX

Recordsnpmupdate-browserslist-db1.3.2

Change the conditions
Fixed
Runtimenode 24 Package version1.3.2 Execution contextnode
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Clear filters

Current conditions

update-browserslist-db @1.3.2windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 4 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
0 / 4
Contract verifications
nothing at this coordinate
Usage records
3
Independent reporting peers
1
Failures with a captured fingerprint
0 / 4
Last recorded
2026-11-04

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

1.3.2

executionContext=node

14 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
escalade 3.2.0 PASS All observations passed contract passed 160 project-days
picocolors 1.1.1 PASS All observations passed contract passed 163 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.

Library1.3.41.3.31.3.21.3.11.3.01.2.3
escalade 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0 3.2.0
picocolors 1.1.1 1.1.1 1.1.1 1.1.1 1.1.1 1.1.1

Moved: 0 · unchanged at every release: 2

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