CodeSampleX

Recordsnpm@asamuzakjp/css-color5.1.11

Change the conditions
Fixed
Runtimenode 24 Package version5.1.11
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@asamuzakjp/css-color @5.1.11windows 11 · x64 · node 24 · npm 11 · 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.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-13

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 1

First observed break

5.1.11

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:529aac3b1da710068c9dcfe93d0864269e86bebfbe110ca5beeed398860460e7

Library Version Health Measured there Projects
@csstools/css-calc 3.3.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@csstools/css-color-parser 4.2.1 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
@csstools/css-color-parser 4.2.2 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@csstools/css-parser-algorithms 4.0.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@csstools/css-tokenizer 4.0.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@asamuzakjp/generational-cache 1.0.1 PASS All observations passed contract passed 3 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.

Moved: 5 · unchanged at every release: 1

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.