CodeSampleX

Recordsnpmwrap-ansi6.2.0wrapAnsi

Change the conditions
Fixed
OSdebian glibc SymbolwrapAnsi
Filter Runtimenode 22 Package version6.2.0 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

wrapAnsi @6.2.0debian glibc · x64 · node 22 · npm · node

1 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 came back clean (1)

Project observations
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

6.2.0

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:4a939d00eec492b9a03b26b042fb8a8194c85e6b0782361ef967eb9b259f03ba

Library Version Health Measured there Projects
ansi-styles 4.3.0 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
string-width 4.2.3 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
strip-ansi 6.0.1 CANDIDATE Correlated change; unproven combination contract passed 23 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: 3 · 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