示例
Enforce asymmetric key constraints including minimum RSA key size, EC named curve matching, and key roles
sha256:70b702f0bec4056d2b1d130f07f566fc2474c24141272abc15d93bb50ad32a34
PUBLISHED
L3_CONTRACT_PASS
MIT-0
执行证据
分开显示声明环境和签名验证运行,明确样本的证明范围。
证据依据签名契约通过
验证回执1
验证级别L3_CONTRACT_PASS
声明的环境
- 执行上下文
- node
- 操作系统
- linux
- 架构
- x64
- 运行时
- node
- 语言
- node
- 包管理器
- npm
验证运行环境
- 执行上下文
- node 22
- 操作系统
- linux alpine · musl
- 架构
- x64
- 运行时
- node 22
- 语言
- javascript
- 包管理器
- npm
- 执行方式
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17
案例
- 目标
- Enforce asymmetric key constraints including minimum RSA key size, EC named curve matching, and key roles HOW
- 包
-
jsonwebtoken 9.0.3
- 环境
- node
- 创建时间
- 2026-08-17T20:01:32Z
常见的想当然
jwt.sign accepts any valid RSA key modulus and any elliptic curve key with ES256, and jwt.verify handles dynamic key resolver callbacks synchronously.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- 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
文件
- NOTES.md
- csx.json
- package-lock.json
- package.json
- src/index.mjs
- test/contract.mjs
下载源代码构件 (tar.gz)
原始种子者
csx-seed
验证回执
- node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9