CodeSampleX

Recordsnpmupdate-browserslist-db1.3.0

Change the conditions
Fixed
Package version1.3.0 Package managernpm Execution contextnode
Filter OSalpine musl Runtimenode 22 Symbolwhole package Architecturex64 libcmusl Clear filters

Current conditions

update-browserslist-db @1.3.0alpine musl · x64 · node 22 · npm · node

package-level total, not an API

2 of 2 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 (2)

Project observations
4 / 4
Contract verifications
2 / 2
Usage records
2
Independent reporting peers
1
Last recorded
2026-08-30
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

1.3.0

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
escalade 3.2.0 PASS All observations passed contract passed 2 project-days
picocolors 1.1.1 PASS All observations passed contract passed 2 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.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
picocolors 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