Runtime evidence / smoke tested
kysely0.29.6
Observed 2026-10-09 14:51 UTC · Linux amd64 / glibc
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_ab51508deb208994caf81cb80f14b800| Runtime | Root import | Root require | Subpath imports | Subpath requires |
|---|---|---|---|---|
| Node.js24.21.0 | Passed | Passed | Passed6 passed · 0 failed | Passed6 passed · 0 failed |
| Node.js26.10.0 | Passed | Passed | Passed6 passed · 0 failed | Passed6 passed · 0 failed |
| Bun1.4.2 | Passed | Passed | Passed6 passed · 0 failed | Passed6 passed · 0 failed |
| Deno2.9.7 | Passed | Passed | Passed6 passed · 0 failed | Passed6 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 kysely 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 kysely work with Node.js?
kysely@0.29.6 passed the applicable loading checks in Node.js 24.21.0. 14 passed · 0 failed.
kysely@0.29.6 passed the applicable loading checks in Node.js 26.10.0. 14 passed · 0 failed.
Does kysely work with Bun?
kysely@0.29.6 passed the applicable loading checks in Bun 1.4.2. 14 passed · 0 failed.
Does kysely work with Deno?
kysely@0.29.6 passed the applicable loading checks in Deno 2.9.7. 14 passed · 0 failed.
Compare npm package compatibility across Node.js, Bun and Deno · Browse observed runtime loading failures
Shared preparation
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.
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 importPassed
6 passed · 0 failed · 6 observed of 6 planned
Node.js 24.21.0 · Subpaths · CommonJS requirePassed
6 passed · 0 failed · 6 observed of 6 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 importPassed
6 passed · 0 failed · 6 observed of 6 planned
Node.js 26.10.0 · Subpaths · CommonJS requirePassed
6 passed · 0 failed · 6 observed of 6 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 importPassed
6 passed · 0 failed · 6 observed of 6 planned
Bun 1.4.2 · Subpaths · CommonJS requirePassed
6 passed · 0 failed · 6 observed of 6 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 importPassed
6 passed · 0 failed · 6 observed of 6 planned
Deno 2.9.7 · Subpaths · CommonJS requirePassed
6 passed · 0 failed · 6 observed of 6 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 ./ec069e1b-8fea-49bc-8b8d-7ee7e183ec97-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
kysely@0.29.6- integrity
sha512-hHaB8C/rfzDDtr/t8YZwxAuPJTT0zHyaPoVzcXwDYhYNAgH/4sIfVhi/XLLIY+bL/FqaIJnjATDbi8ObSELmxg==- tarball
https://registry.npmjs.org/kysely/-/kysely-0.29.6.tgz- snapshot
a305b8bc-0850-4bcf-aeca-5a0354a45d07- generation
9c4a3162-0ef4-4dfe-a9b4-751a2b5f5e42- lockDigest
c0082beff2d15edbfd1ab18855b8c88cad66f3f562e8c30722d10dc8ed498dec- treeDigest
8df3c14491b834526654b844a5010d0a6a970b84c78590d82eca819ae16a181f- 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-09T14:51:06.253Z
node_24_21_0
sha256:f2fcbb4dfbd6d5f57f4e43de97e70182d9982ac7cc0cc063dfff2cf1759a411d
Built 2026-10-04 15:20 UTC · runtime_image_v1
node_26_10_0
sha256:9c1c93cc35d1408d26a61c4efccbde37c35425e362a2e723b885c3333d2be073
Built 2026-10-04 15:20 UTC · runtime_image_v1
bun_1_4_2
sha256:2343363679fb92d59a395ff081b783b5514f06295b1bc6d61baaeef17e793789
Built 2026-10-04 15:21 UTC · runtime_image_v1
deno_2_9_7
sha256:4292bb23555f98fb9dfc30fb447daa1c301686d89264fd8643ccb86bc0d53c29
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.