CodeSampleX

Recordsnpm@asamuzakjp/css-color5.1.11

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

Current conditions

@asamuzakjp/css-color @5.1.11ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 4 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
2 / 2
Contract verifications
0 / 4
Independent reporting peers
1
Last recorded
2026-08-30

Dependencies

LibraryVersionMeasured thereProjects
@asamuzakjp/generational-cache 1.0.1 contract passed 1 project-day
@csstools/css-calc 3.3.0 contract passed 1 project-day
@csstools/css-color-parser 4.2.1 contract passed 1 project-day
@csstools/css-parser-algorithms 4.0.0 contract passed 1 project-day
@csstools/css-tokenizer 4.0.0 contract passed 1 project-day

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.

Library5.1.113.2.0
@csstools/css-calc 3.3.0 2.1.4
@csstools/css-color-parser 4.2.1 3.1.0
@csstools/css-parser-algorithms 4.0.0 3.0.5
@csstools/css-tokenizer 4.0.0 3.0.4
@asamuzakjp/generational-cache 1.0.1
lru-cache 10.4.3

Moved: 4 · 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