CodeSampleX

Recordsnpmupdate-browserslist-db1.3.1

Change the conditions
Fixed
OSdebian glibc Package version1.3.1
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

update-browserslist-db @1.3.1debian glibc · x64 · node 22 · npm · 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 (2)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 2

First observed break

1.3.1

linux · node@22.23 · executionContext=node

12 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
escalade 3.2.0 PASS All observations passed contract passed 32 project-days
picocolors 1.1.1 PASS All observations passed contract passed 21 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