CompatLab
Choose a version or request a scan

@stellarforge-protocol/sdk0.3.0

Node.js, Bun and Deno compatibility results

Does @stellarforge-protocol/sdk 0.3.0 load in Node.js, Bun and Deno? In the recorded environment, the results were Node.js 24.21.0: passed; Node.js 26.10.0: passed; Bun 1.4.2: passed; Deno 2.9.7: passed. All applicable planned checks completed. Loading success does not establish functional correctness or package safety.

Observed 2026-10-17 07:18 UTC · Linux amd64 / glibc

Loading results

Loading outcomes by runtime and consumer mode
RuntimeRoot importRoot requireSubpath importsSubpath requires
Node.js24.21.0PassedPassedNot applicable0 passed · 0 failedNot applicable0 passed · 0 failed
Node.js26.10.0PassedPassedNot applicable0 passed · 0 failedNot applicable0 passed · 0 failed
Bun1.4.2PassedPassedNot applicable0 passed · 0 failedNot applicable0 passed · 0 failed
Deno2.9.7PassedPassedNot applicable0 passed · 0 failedNot applicable0 passed · 0 failed

Import uses ESM; require uses CommonJS. Results cover the package root and selected explicit subpaths. Select a result to inspect its evidence.

Does @stellarforge-protocol/sdk 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 @stellarforge-protocol/sdk work with Node.js?

@stellarforge-protocol/sdk@0.3.0 passed the applicable loading checks in Node.js 24.21.0. 2 passed · 0 failed.

@stellarforge-protocol/sdk@0.3.0 passed the applicable loading checks in Node.js 26.10.0. 2 passed · 0 failed.

Does @stellarforge-protocol/sdk work with Bun?

@stellarforge-protocol/sdk@0.3.0 passed the applicable loading checks in Bun 1.4.2. 2 passed · 0 failed.

Does @stellarforge-protocol/sdk work with Deno?

@stellarforge-protocol/sdk@0.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 @stellarforge-protocol/sdk@0.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

Source evidence and limitations

This page selects an eligible observation for this exact version, preferring the current environment. The selection can change after a rescan or reclassification. Cite the observation link below when referring to these results.

Full report and provenanceCompact JSONReport history

Matrix production_2db44d825b68aeb5839111e38b0ad23c · Classifier classifier_v3 · Install scripts disabled

  • 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.
How the tests work