Runtime evidence / smoke tested
string-width 9.0.0
Observed 2026-11-13 16:33 UTC · Linux amd64 / glibc
Classified 2026-11-13 16:33 UTC · classifier_v3
Version summary · Observation 0 · Report history · Maintainer tools (coming soon)
All applicable planned loading observations completed.
This is loading evidence. It does not establish functional correctness or package safety.
Runtime matrix
4 pinned runtimes · production_ca37634d0b1dea7c6bdc9cc4f8db1c9f| Runtime | Root import | Root require | Subpath imports | Subpath requires |
|---|---|---|---|---|
| Node.js24.21.0 | Passed | Passed | Not applicable0 passed · 0 failed | Not applicable0 passed · 0 failed |
| Node.js26.10.0 | Passed | Passed | Not applicable0 passed · 0 failed | Not applicable0 passed · 0 failed |
| Bun1.4.2 | Passed | Passed | Not applicable0 passed · 0 failed | Not applicable0 passed · 0 failed |
| Deno2.9.7 | Passed | Passed | Not applicable0 passed · 0 failed | Not applicable0 passed · 0 failed |
Node.js 26.10.0
Bun 1.4.2
Deno 2.9.7
Import uses ESM; require uses CommonJS. Root modes use fresh sandboxes. Subpath batches share module caches and globals. Select a result to inspect its evidence.
Does string-width work in Node.js, Bun and Deno?
All applicable planned loading checks completed. The runtimes used the same installed dependency snapshot. Test environment: Linux amd64 / glibc, with install scripts and execution networking disabled. A pass means import or require resolved the entry and ran its module code; the check did not call any export.
Does string-width work with Node.js?
string-width@9.0.0 passed the applicable loading checks in Node.js 24.21.0. 2 passed · 0 failed.
string-width@9.0.0 passed the applicable loading checks in Node.js 26.10.0. 2 passed · 0 failed.
Does string-width work with Bun?
string-width@9.0.0 passed the applicable loading checks in Bun 1.4.2. 2 passed · 0 failed.
Does string-width work with Deno?
string-width@9.0.0 passed the applicable loading checks in Deno 2.9.7. 2 passed · 0 failed.
Next test after a loading pass
A loading pass does not cover errors or unexpected values that appear later, when your application calls the package or the package calls Node.js APIs.
Call the operation your application needs from string-width@9.0.0 in the recorded runtime version and in a runtime where it works, then compare the returned values or errors. To report a difference upstream, include the public package version, import path, failing call, runtime versions, operating system and architecture, never credentials or private code.
Compare npm package compatibility across Node.js, Bun and Deno · Browse observed runtime loading failures
Shared preparation
4 installed packages · 0 optional dependencies omitted · lifecycle scripts disabled
The omitted count covers locked optional dependencies. Optional peers are separate and are not automatically installed.
Static manifest, native and script observations
Static indicators are context; their presence alone does not establish a prerequisite or failure.
Coverage and evidence
Node.js 24.21.0 · Root · ESM importPassed
1 passed · 0 failed · 1 observed of 1 planned
Node.js 24.21.0 · Root · CommonJS requirePassed
1 passed · 0 failed · 1 observed of 1 planned
Node.js 24.21.0 · Subpaths · ESM importNot applicable
0 passed · 0 failed · 0 observed of 0 planned
Node.js 24.21.0 · Subpaths · CommonJS requireNot applicable
0 passed · 0 failed · 0 observed of 0 planned
Node.js 26.10.0 · Root · ESM importPassed
1 passed · 0 failed · 1 observed of 1 planned
Node.js 26.10.0 · Root · CommonJS requirePassed
1 passed · 0 failed · 1 observed of 1 planned
Node.js 26.10.0 · Subpaths · ESM importNot applicable
0 passed · 0 failed · 0 observed of 0 planned
Node.js 26.10.0 · Subpaths · CommonJS requireNot applicable
0 passed · 0 failed · 0 observed of 0 planned
Bun 1.4.2 · Root · ESM importPassed
1 passed · 0 failed · 1 observed of 1 planned
Bun 1.4.2 · Root · CommonJS requirePassed
1 passed · 0 failed · 1 observed of 1 planned
Bun 1.4.2 · Subpaths · ESM importNot applicable
0 passed · 0 failed · 0 observed of 0 planned
Bun 1.4.2 · Subpaths · CommonJS requireNot applicable
0 passed · 0 failed · 0 observed of 0 planned
Deno 2.9.7 · Root · ESM importPassed
1 passed · 0 failed · 1 observed of 1 planned
Deno 2.9.7 · Root · CommonJS requirePassed
1 passed · 0 failed · 1 observed of 1 planned
Deno 2.9.7 · Subpaths · ESM importNot applicable
0 passed · 0 failed · 0 observed of 0 planned
Deno 2.9.7 · Subpaths · CommonJS requireNot applicable
0 passed · 0 failed · 0 observed of 0 planned
Planner omissions
- pattern
- 0
- non executable
- 0
- not exported
- 0
- invalid subpath
- 0
- coverage limit
- 0
Reproduce these inputs
Download the recorded inputs and exact dependency lock. These files do not include the CLI, runtime images or installed packages.
Local replay requires setup. The CLI currently runs from the CompatLab source repository on a qualified Linux amd64/runsc host. Hosted runtime images are not yet distributed for public download; an operator must supply the exact images named in this report. A fresh image build does not substitute for them. CLI setup and replay requirements
Command for a configured host
Run from the built CompatLab repository with both downloads in that directory and the exact runtime images loaded. Rebuilding creates a new snapshot generation.
sudo "$(command -v node)" apps/cli/dist/bin.js reproduce ./8d8fa5e2-1c74-41e0-83cc-a89d1b7dcba0-reproduction.json --rebuild --lockfile ./package-lock.json --jsonThe original worker last reported its sealed snapshot as available. Verified reuse requires those actual bytes in your local state directory.
Exact provenance
- artifact
string-width@9.0.0- integrity
sha512-2MOboAIRIszVGZVPA2Zqwj0ujd0o+xAZ5y2ft4OcD4kuVQ4phZxq0Sv7YTY8yaDA2CSMXch1EWTkJw+tTJZTzA==- tarball
https://registry.npmjs.org/string-width/-/string-width-9.0.0.tgz- snapshot
584e0d70-fa7b-4c39-851b-ef1ab3b3c5f1- generation
5263e8ea-8aca-43b4-9ec8-beb7d1d6a7ad- lockDigest
93e50d5f588b3134197d6c0cd48e2bc2ad25b9bf3c93f0cd4736b75146ba908f- treeDigest
6f37dc547af66dad8391d3cb5778a7e5067dca5c6a3cdc6c016d76ae95a88386- installerImage
node:24.21.0-bookworm-slim@sha256:5cbc7caba8c2c0f0bca675d1b61b9f2857e1cf1853c6164ee9dd409501a936e7- preparationProfile
npm_11_19_0_linux_amd64_v2- harness
load_v2- planner
explicit_exports_v1- policy
runtime_limits_v2- classifier
classifier_v3- classifiedAt
2026-11-13T16:33:38.274Z
node_24_21_0
sha256:b8d7f578e8f18085395cd4447d23b6ac972629e1eaffd0302f5545d94f2f097d
Built 2026-10-04 15:20 UTC · runtime_image_v1
node_26_10_0
sha256:914c559b7a1cd7e37257d0d39be087922d4fc369d61670b7e0a892c528754c4d
Built 2026-10-04 15:20 UTC · runtime_image_v1
bun_1_4_2
sha256:1b71c2c66399e396c5847ed10240bacc92a3a17eedd3d9313ce4ee5e1dc9942a
Built 2026-10-04 15:21 UTC · runtime_image_v1
deno_2_9_7
sha256:895a637dbf9471deafcf853e1d2b90bdcd3ed96e10d4a95bb62d246fc778a375
Built 2026-10-04 15:21 UTC · runtime_image_v1
Evidence limitations
- Only installation and loading were observed; functional correctness and package safety are not established.
- Subpath batches share module caches and globals; root modes use separate fresh sandboxes.
- Package-visible harness observations can be tampered with. They are not adversarial attestation.
- Evidence applies to these exact artifacts, dependency snapshot, runtime images and Linux amd64/glibc policy.
- Runtime error codes are captured observations and can also be thrown by package code.