Choose a version or request a scan

pino10.4.0

Node.js, Bun and Deno compatibility results

Does pino 10.4.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-09 10:15 UTC · Linux amd64 / glibc

Loading results

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

Does pino 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 pino work with Node.js?

pino@10.4.0 passed the applicable loading checks in Node.js 24.21.0. 2 passed · 0 failed.

pino@10.4.0 passed the applicable loading checks in Node.js 26.10.0. 2 passed · 0 failed.

Does pino work with Bun?

pino@10.4.0 passed the applicable loading checks in Bun 1.4.2. 2 passed · 0 failed.

Does pino work with Deno?

pino@10.4.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

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.

Matrix production_ce416e976d3b4c51b252859d31c1fa7c · Classifier classifier_v2 · 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