CodeSampleX

Recordsnpmstring-width5.1.2

Change the conditions
Fixed
Package version5.1.2 Architecturex64 Package managernpm
Filter OSalpine musl Runtimenode 22 Symbolwhole package 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

Dependencies

LibraryVersionMeasured thereProjects
eastasianwidth 0.2.0 contract passed 5 project-days
emoji-regex 9.2.2 contract passed 5 project-days
strip-ansi 7.2.0 contract passed 5 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.

Library5.1.24.2.3
emoji-regex 9.2.2 8.0.0
strip-ansi 7.2.0 6.0.1
eastasianwidth 0.2.0
is-fullwidth-code-point 3.0.0

Moved: 2 · unchanged at every release: 2

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