"JSON Web Almost Everything" - JWA, JWS, JWE, JWT, JWK, JWKS for Node.js, Browser, Cloudflare Workers, Deno, and other Web-interoperable runtimes.

The following specifications are implemented by jose

• JSON Web Signature (JWS) - RFC7515
• JSON Web Encryption (JWE) - RFC7516
• JSON Web Key (JWK) - RFC7517
• JSON Web Algorithms (JWA) - RFC7518
• JSON Web Token (JWT) - RFC7519
• JSON Web Key Thumbprint - RFC7638
• JSON Web Key Thumbprint URI - RFC9278
• JWS Unencoded Payload Option - RFC7797
• CFRG Elliptic Curve ECDH and Signatures - RFC8037
• secp256k1 EC Key curve support - JOSE Registrations for WebAuthn Algorithms

The test suite utilizes examples defined in RFC7520 to confirm its JOSE implementation is correct.

example ESM import

import * as jose from 'jose'

example CJS require

const jose = require('jose')

example Deno import

import * as jose from 'https://deno.land/x/jose/index.ts'

• JSON Web Tokens (JWT)
  • Signing
  • Verification & JWT Claims Set Validation
  • Encrypted JSON Web Tokens
    • Encryption
    • Decryption & JWT Claims Set Validation
• Key Import
  • JWK Import
  • Public Key Import (SPKI)
  • Public Key Import (X.509 Certificate)
  • Private Key Import (PKCS #8)
• JSON Web Encryption (JWE)
  • Encryption - Compact, Flattened, General
  • Decryption - Compact, Flattened, General
• JSON Web Signature (JWS)
  • Signing - Compact, Flattened, General
  • Verification - Compact, Flattened, General
• JSON Web Key (JWK)
  • Calculating JWK Thumbprint
  • Calculating JWK Thumbprint URI
  • Verification using a JWK Embedded in a JWS Header
• JSON Web Key Set (JWKS)
  • Verify using a local JWKSet
  • Verify using a remote JWKSet
• Key Pair or Secret Generation
  • Asymmetric Key Pair Generation
  • Symmetric Secret Generation
• Key Export
  • JWK Export
  • Private Key Export
  • Public Key Export
• Utilities
  • Decoding Token's Protected Header
  • Decoding JWT Claims Set
• Unsecured JWT
• JOSE Errors

• Browser Support
• Cloudflare Workers Support
• Deno Support
• Electron Support
• Next.js Middleware / Vercel Edge Functions Support
• Node.js Support

Yes. All module's public API is subject to Semantic Versioning 2.0.0.

• it supports Browser, Deno, Cloudflare Workers, and other Web-interoperable runtimes
• it supports encrypted JWTs (i.e. in JWE format)
• supports secp256k1, Ed25519, Ed448, X25519, and X448
• it supports JWK Key Format for all four key types (oct, RSA, EC and OKP)
• it is exclusively using native platform Key object representations (CryptoKey and KeyObject)
• there is JSON Web Encryption support
• it supports the General and Flattened JSON Serialization Syntaxes
• it supports the "crit" member validations to make sure extensions are handled correctly

node-jose is built to work in any javascript runtime, to be able to do that it packs a lot of polyfills and javascript implementation code in the form of node-forge, this significantly increases the footprint of the modules with dependencies that either aren't ever used or have native implementation available in the runtime already, those are often times faster and more reliable.

• supports secp256k1, Ed25519, Ed448, X25519, and X448

• Whenever Uint8Array is a valid input, so is Buffer since buffers are instances of Uint8Array.
• Whenever Uint8Array is returned and you want a Buffer instead, use Buffer.from(uint8array).

Yes the bundle size is on the larger side, that is because each module is actually published multiple times so that it can remain truly without dependencies and be universal / isomorphic.

Nevertheless, since each module can be required independently and is fully tree-shakeable, the install size should not be a cause for concern.