msgpackr

Ultra-fast MessagePack implementation with extensions for records and structured cloning

msgpackr@2.1.3 was published on 2026-10-28. Its manifest declares 0 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All msgpackr versions · Permanent reference to 2.1.3

Package specifications

Version2.1.3
License declarationMIT
Published2026-10-28T18:36:45.144Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count1
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size2259.10 KiB
Published file count33
Package typemodule
ES module entry./index.js
Default entry./dist/node.cjs
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars694
Repository forks72

Install msgpackr 2.1.3

npm install msgpackr@2.1.3
pnpm add msgpackr@2.1.3
yarn add msgpackr@2.1.3

Runtime dependencies

  • None declared

Peer requirements

  • None declared

Optional dependencies

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.

Code-Review1/10 — Found 4/27 approved changesets -- score normalized to 1
Security-Policy10/10 — security policy file detected
Maintained5/10 — 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness