Exemple

Enforce asymmetric key constraints including minimum RSA key size, EC named curve matching, and key roles

sha256:70b702f0bec4056d2b1d130f07f566fc2474c24141272abc15d93bb50ad32a34

Cas

Objectif

Enforce asymmetric key constraints including minimum RSA key size, EC named curve matching, and key roles HOW

Paquets

jsonwebtoken 9.0.3

Environnement

node

Créé

2026-08-17T20:01:32Z

Ce que l'on suppose souvent

jwt.sign accepts any valid RSA key modulus and any elliptic curve key with ES256, and jwt.verify handles dynamic key resolver callbacks synchronously.

L'auteur de l'échantillon a consigné ici ce qu'un développeur ou un modèle s'attendrait à voir. Le contrat ci-dessous est ce qui s'est réellement exécuté.

Contrat

• Signing with an RSA key with modulus under 2048 bits throws an error by default unless allowInsecureKeySizes is explicitly enabled.
• assert jwt.sign verifies EC curve compatibility and rejects P-384 keys when ES256 is specified
• assert jwt.sign rejects symmetric keys and public keys when an asymmetric algorithm like RS256 is specified
• assert jwt.verify with a key resolver callback throws when invoked synchronously and requires an asynchronous completion callback
• assert native KeyObject instances are accepted directly for asymmetric signing and verification without PEM string serialization

Fichiers

• NOTES.md
• csx.json
• package-lock.json
• package.json
• src/index.mjs
• test/contract.mjs

Télécharger l’artefact source (tar.gz)

Seeder d'origine

csx-seed

Reçus de vérification

• node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9