Runtime evidence / smoke tested

is-number7.0.0

Observed 2026-10-04 18:03 UTC · Linux amd64 / glibc

Download JSON

Version summary · Observation 1 · Report history · Maintainer tools (coming soon)

Passed

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_bdecc487edb3cbaeb508c4b7eeb02359

Loading outcomes by runtime and consumer mode
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 24.21.0

Root importPassed

Root requirePassed

Subpath importsNot applicable0 passed · 0 failed

Subpath requiresNot applicable0 passed · 0 failed

Node.js 26.10.0

Root importPassed

Root requirePassed

Subpath importsNot applicable0 passed · 0 failed

Subpath requiresNot applicable0 passed · 0 failed

Bun 1.4.2

Root importPassed

Root requirePassed

Subpath importsNot applicable0 passed · 0 failed

Subpath requiresNot applicable0 passed · 0 failed

Deno 2.9.7

Root importPassed

Root requirePassed

Subpath importsNot applicable0 passed · 0 failed

Subpath requiresNot applicable0 passed · 0 failed

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 is-number 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. Successful import or require does not prove that package functions, native features or your application work.

Does is-number work with Node.js?

is-number@7.0.0 passed the applicable loading checks in Node.js 24.21.0. 2 passed · 0 failed.

is-number@7.0.0 passed the applicable loading checks in Node.js 26.10.0. 2 passed · 0 failed.

Does is-number work with Bun?

is-number@7.0.0 passed the applicable loading checks in Bun 1.4.2. 2 passed · 0 failed.

Does is-number work with Deno?

is-number@7.0.0 passed the applicable loading checks in Deno 2.9.7. 2 passed · 0 failed.

Compare npm package compatibility across Node.js, Bun and Deno · Browse observed runtime loading failures

Shared preparation

Passed

1 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.

{
  "native": {
    "count": 0,
    "paths": [],
    "buildIndicators": [],
    "prerequisiteProven": false
  },
  "declared": {
    "main": "index.js",
    "engines": {
      "node": ">=0.12.0"
    },
    "scripts": {
      "test": "mocha"
    },
    "devDependencies": {
      "ansi": "^0.3.1",
      "mocha": "^3.5.3",
      "benchmark": "^2.1.4",
      "gulp-format-md": "^1.0.0"
    }
  },
  "platform": {
    "os": true,
    "cpu": true,
    "libc": true
  },
  "evidenceLevel": "static_only",
  "lifecycleScripts": []
}

Coverage and evidence

Node.js 24.21.0 · Root · ESM importPassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON

Node.js 24.21.0 · Root · CommonJS requirePassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON

Node.js 24.21.0 · Subpaths · ESM importNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON

Node.js 24.21.0 · Subpaths · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON

Node.js 26.10.0 · Root · ESM importPassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON

Node.js 26.10.0 · Root · CommonJS requirePassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON

Node.js 26.10.0 · Subpaths · ESM importNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON

Node.js 26.10.0 · Subpaths · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON

Bun 1.4.2 · Root · ESM importPassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON

Bun 1.4.2 · Root · CommonJS requirePassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON

Bun 1.4.2 · Subpaths · ESM importNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON

Bun 1.4.2 · Subpaths · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON

Deno 2.9.7 · Root · ESM importPassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON

Deno 2.9.7 · Root · CommonJS requirePassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON

Deno 2.9.7 · Subpaths · ESM importNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON

Deno 2.9.7 · Subpaths · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON

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.

Reproduction inputs Exact package lock

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 ./9be21cb0-e15b-45f6-859c-16de285b0f54-reproduction.json --rebuild --lockfile ./package-lock.json --json

The original worker last reported its sealed snapshot as available. Verified reuse requires those actual bytes in your local state directory.

Exact provenance

artifact: is-number@7.0.0
integrity: sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==
tarball: https://registry.npmjs.org/is-number/-/is-number-7.0.0.tgz
snapshot: 6a3ff081-ebc6-46f3-b0b6-766b5837265c
generation: 5920393c-9385-4350-a9bc-ab24427b62ba
lockDigest: aa00182f1fe395195a34c4bc737192838ddd95830f12345dd735e46b90cc8172
treeDigest: 25ce1e55ec0e3209c75cb53bac337372b6b949ebae5223555d1af59d1b64e509
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_v2
classifiedAt: 2026-10-09T05:14:24.656Z

node_24_21_0

sha256:f1c6953762816b7e98e53f6a7e9ef440dcc0c91bcec33592c6629877a480d0eb

Built 2026-10-04 15:20 UTC · runtime_image_v1

node_26_10_0

sha256:cd3253851abd920d46d1462274fa28db24a45440486a77e0f7ce92d722b97fc3

Built 2026-10-04 15:20 UTC · runtime_image_v1

bun_1_4_2

sha256:1b3e67fa6ea782e902fb8566fcf25a29021e7b98748e09399b03782f0207edd6

Built 2026-10-04 15:21 UTC · runtime_image_v1

deno_2_9_7

sha256:4e9d7cd1242ce2d79cec68223828fb45b7234a9b253388c14bea2c54cd744311

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.