← Package details

Runtime evidence / smoke tested

crypto-vdf1.3.0

Observed 2026-10-17 05:20 UTC · Linux amd64 / glibc

Classified 2026-10-17 05:20 UTC · classifier_v3

Download JSON
Immutable loading evidence badge for crypto-vdf
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_2db44d825b68aeb5839111e38b0ad23c

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 crypto-vdf 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 crypto-vdf work with Node.js?

crypto-vdf@1.3.0 passed the applicable loading checks in Node.js 24.21.0. 2 passed · 0 failed.

crypto-vdf@1.3.0 passed the applicable loading checks in Node.js 26.10.0. 2 passed · 0 failed.

Does crypto-vdf work with Bun?

crypto-vdf@1.3.0 passed the applicable loading checks in Bun 1.4.2. 2 passed · 0 failed.

Does crypto-vdf work with Deno?

crypto-vdf@1.3.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 crypto-vdf@1.3.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

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.

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.

    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 ./8d2333d1-b011-47d3-b360-69f9ac303c35-reproduction.json --rebuild --lockfile ./package-lock.json --json

    The recorded worker snapshot is unavailable. Retained identity and lock bytes do not guarantee a successful rebuild.

    Exact provenance
    artifact
    crypto-vdf@1.3.0
    integrity
    sha512-hsfRw5ChPj8CC29keySxOlx+agC4GpS4QqRZn4VevKXHbeYhZtTbJ6fE33Y60S5DRnPmQs1bkLuGMZEgK8WZqQ==
    tarball
    https://registry.npmjs.org/crypto-vdf/-/crypto-vdf-1.3.0.tgz
    snapshot
    60a49243-179b-4aae-bd56-b4beb4c64535
    generation
    162daa4c-4fc4-430a-b9d0-87083fb6efd4
    lockDigest
    ab7f583d4e61dcf82b21d746534ac59c0405a7f96fb2eb62d1f38077eb78270e
    treeDigest
    cde15551ea41d6931b5103d47e55e7068f142210346948e35c548edda19b3db3
    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-10-17T05:20:42.239Z

    node_24_21_0

    sha256:12a6a4db05cc9f4f55fe7e4731983c5476658c748b722cac3332c4bfc986c2f1

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

    node_26_10_0

    sha256:8cef3b37b8edb5af9da80cb7416bd2c8b35b87fea1bc72c9abbb204ee000bd9c

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

    bun_1_4_2

    sha256:6d19a3cc65d5015ba20193b7610af27ad603eed4ea29caf4dd4ccc04ad5ca7ef

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

    deno_2_9_7

    sha256:1a5c5f412e04bff71a674b122f4216fac988b0fddc9d36be588224490adc292e

    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.