jsonwebtoken 3.2.2

JSON Web Token implementation (symmetric and asymmetric)

jsonwebtoken@3.2.2 was published on 2015-01-15. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: Critical vulnerability fix in v5.0.0. See https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/

All jsonwebtoken versions · Permanent reference to 3.2.2 · Latest release

Package specifications

Version3.2.2
License declarationMIT
Published2015-01-15T15:17:52.808Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories4
Resolved graph dependencies24
Repository stars18180
Repository forks1298

Install jsonwebtoken 3.2.2

npm install jsonwebtoken@3.2.2
pnpm add jsonwebtoken@3.2.2
yarn add jsonwebtoken@3.2.2

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.

Known direct advisories

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
Binary-Artifacts10/10 — no binaries found in the repo
Code-Review8/10 — Found 24/28 approved changesets -- score normalized to 8
Maintained0/10 — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
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
Packaging10/10 — packaging workflow detected
Branch-Protection5/10 — branch protection is not maximal on development and all release branches
Security-Policy10/10 — security policy file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness