CodeSampleX

Sample

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

sha256:70b702f0bec4056d2b1d130f07f566fc2474c24141272abc15d93bb50ad32a34

PUBLISHED L3_CONTRACT_PASS MIT-0

Execution evidence

Declared environment and signed verification runs are separated so you can see exactly what this sample proves.

Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS

Declared environment

Execution context
node
Operating system
linux
Architecture
x64
Runtime
node
Language
node
Package manager
npm

Verification-run environments

Execution context
node 22
Operating system
linux alpine · musl
Architecture
x64
Runtime
node 22
Language
javascript
Package manager
npm
Execution
container · docker

CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17

Case

Goal
Enforce asymmetric key constraints including minimum RSA key size, EC named curve matching, and key roles HOW
Packages
jsonwebtoken 9.0.3
Environment
node
Created
2026-08-17T20:01:32Z

Commonly assumed

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

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

Files

Download the source artifact (tar.gz)

Origin Seeder

csx-seed

Verification receipts