CodeSampleX

Recordsnpmwrap-ansi8.1.0

Change the conditions
Fixed
Package version8.1.0 Package manageryarn 4 Execution contextnode
Filter OSubuntu glibc Runtimenode 22 Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

wrap-ansi @8.1.0ubuntu glibc · x64 · node 22 · yarn 4 · node

package-level total, not an API

3 of 3 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (2)

Project observations
3 / 3
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-07
Evidence you can open

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 · moduleSystem=cjs · executionContext=node

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

View exact conditions View failure cluster
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.

Library9.0.28.1.07.0.06.2.0
ansi-styles 6.2.3 6.2.3 4.3.0 4.3.0
string-width 7.2.0 5.1.2 4.2.3 4.2.3
strip-ansi 7.2.0 7.1.2 6.0.1 6.0.1

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