superjson 2.2.5

- 🍱 Reliable serialization and deserialization - 🔐 Type safety with autocompletion - 🐾 Negligible runtime footprint - 💫 Framework agnostic - 🛠 Perfect fix for Next.js's serialisation limitations in `getServerSideProps` and `getInitialProps`

superjson@2.2.5 was published on 2025-10-28. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=16.

All superjson versions · Permanent reference to 2.2.5 · Latest release

Package specifications

Version2.2.5
License declarationMIT
Published2025-10-28T14:36:36.188Z
Node.js requirement>=16
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size161.23 KiB
Published file count78
Package typemodule
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars5288
Repository forks134

Install superjson 2.2.5

npm install superjson@2.2.5
pnpm add superjson@2.2.5
yarn add superjson@2.2.5

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained1/10 — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Code-Review8/10 — Found 21/26 approved changesets -- score normalized to 8
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness