CodeSampleX

Recordsnpm@csstools/css-color-parser4.2.2

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

Current conditions

@csstools/css-color-parser @4.2.2ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 1 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
4 / 4
Contract verifications
0 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-06
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

4.2.2

linux · node@22.23 · moduleSystem=cjs · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:f0ffff252e3f94518ed1f8821bf9fcf877e30b2d5cf79818540559f03f269589

View exact conditions View failure cluster
Library Version Health Measured there Projects
@csstools/color-helpers 6.1.1 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
@csstools/css-calc 3.3.0 CANDIDATE Correlated change; unproven combination contract passed 4 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.

Library4.2.24.2.13.1.0
@csstools/color-helpers 6.1.1 — 5.1.0
@csstools/css-calc 3.3.0 3.3.0 2.1.4

Moved: 2 · unchanged at every release: 0

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