jsonwebtoken 1.0.2
JSON Web Token implementation (symmetric and asymmetric)
jsonwebtoken@1.0.2 was published on 2014-08-23. 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 1.0.2 · Latest release
Package specifications
| Version | 1.0.2 |
|---|---|
| License declaration | MIT |
| Published | 2014-08-23T22:59:10.227Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 4 |
| Resolved graph dependencies | 3 |
| Repository stars | 18180 |
| Repository forks | 1298 |
Install jsonwebtoken 1.0.2
npm install jsonwebtoken@1.0.2 pnpm add jsonwebtoken@1.0.2 yarn add jsonwebtoken@1.0.2
Runtime dependencies
- jws ~0.2.6
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.
- base64url@0.0.6 — indirect
- jwa@0.0.1 — indirect
- jws@0.2.6 — direct
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-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 8/10 — Found 24/28 approved changesets -- score normalized to 8 |
| Maintained | 0/10 — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 4/10 — dependency not pinned by hash detected -- score normalized to 4 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Packaging | 10/10 — packaging workflow detected |
| Branch-Protection | 5/10 — branch protection is not maximal on development and all release branches |
| Security-Policy | 10/10 — security policy file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/jsonwebtoken/1.0.2 — retrieved 2026-10-29T13:25:16.660Z
- https://api.deps.dev/v3/projects/github.com%2Fauth0%2Fnode-jsonwebtoken — retrieved 2026-10-29T11:10:08.340Z
- https://api.deps.dev/v3/systems/npm/packages/jsonwebtoken/versions/1.0.2 — retrieved 2026-10-29T13:25:17.177Z
- https://api.deps.dev/v3/systems/npm/packages/jsonwebtoken/versions/1.0.2:dependencies — retrieved 2026-10-29T13:25:17.192Z