Recordsnpmjose6.2.9jwtVerify
OS × runtime at a glance
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Published samples
- jose 6.2.9: Setting maxTokenAge in jwtVerify enforces mandatory presence of the iat claim, rejecting tokens without iat via JWTClaimValidationFailed even if unexpired by exp, and rejects future iat timestamps unless clockTolerance is configured. This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWjwtVerifynode MIT-0 · 2026-08-17
Compatibility matrix
Project-level observations and symbol/contract verifications are counted separately and never combined.
These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.
| Environment | Confidence | Observations | Verified | Pass rate | Peers | Last seen |
|---|---|---|---|---|---|---|
| node 22 · JS · npm · linux musl · docker
Verified: CONTRACT 2✓
|
MEDIUM | 0 | 2 | 100% | 0 · 2✓ | 2026-08-18 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 1✓
|
LOW | 1 | 0 | 100% | 1 | 2026-08-29 |
snapshot · 2026-08-30
Failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×6 6.2.4 → 6.2.8 → 6.2.9 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-14 · Last seen: 2026-08-21Diagnostic re-verification candidate