CodeSampleX

Recordsnpmcolor-convert2.0.1

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

Current conditions

color-convert @2.0.1windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 68 passed

Verified — this network ran a contract at this coordinate.

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

Project observations
179 / 264
Contract verifications
0 / 68
Usage records
334
Independent reporting peers
1
Failures with a captured fingerprint
78 / 85
Last recorded
2026-09-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

2.0.1

windows · node@24.13 · moduleSystem=esm · executionContext=node

31 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

Library Version Health Measured there Projects
color-name 1.1.4 CANDIDATE Correlated change; unproven combination contract passed 178 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.

Library2.0.11.9.3
color-name 1.1.4 1.1.3

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

Showing the 12 most-reported of 299 recorded failure clusters. The rest are single reports.