CodeSampleX

Recordsnpmupdate-browserslist-db1.3.2

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

Current conditions

update-browserslist-db @1.3.2ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 10 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
52 / 52
Contract verifications
0 / 10
Usage records
17
Independent reporting peers
2
Last recorded
2026-08-31

Dependencies

LibraryVersionMeasured thereProjects
escalade 3.2.0 contract passed 6 project-days
picocolors 1.1.1 contract passed 6 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.21.3.11.3.01.2.3
escalade 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

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