CodeSampleX

Recordsnpmstring-width5.1.2

Change the conditions
Fixed
OSalpine musl Package version5.1.2
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

string-width @5.1.2alpine musl · x64 · node 22 · npm · node

package-level total, not an API

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
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-30
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 1

First observed break

5.1.2

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
emoji-regex 9.2.2 CANDIDATE Correlated change; unproven combination contract passed 54 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 56 project-days
eastasianwidth 0.2.0 PASS All observations passed contract passed 52 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.

Library8.2.27.2.05.1.24.2.3
emoji-regex — 10.6.0 9.2.2 8.0.0
strip-ansi 7.2.0 7.2.0 7.1.2 6.0.1
eastasianwidth — — 0.2.0 —
get-east-asian-width 1.6.0 1.6.0 — —
is-fullwidth-code-point — — — 3.0.0

Moved: 2 · unchanged at every release: 3

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