CodeSampleX

Recordsnpmwrap-ansi8.1.0wrapAnsi

Change the conditions
Fixed
Package version8.1.0 SymbolwrapAnsi
Filter OSalpine musl Runtimenode 22 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

wrapAnsi @8.1.0alpine musl · 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
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-21

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 0

First observed break

8.1.0

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

8 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

Library Version Health Measured there Projects
ansi-styles 6.2.3 CANDIDATE Correlated change; unproven combination contract passed 22 project-days
string-width 5.1.2 CANDIDATE Correlated change; unproven combination contract passed 25 project-days
strip-ansi 7.1.2 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
strip-ansi 7.2.0 CANDIDATE Correlated change; unproven combination contract passed 24 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