Recordsnpmjose6.2.9CompactSign
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: Sign and verify compact JWS with CompactSign and compactVerify in jose 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. HOWCompactSigncompactVerify MIT-0 · 2026-08-26
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 1✓
|
LOW | 0 | 1 | 100% | 0 · 1✓ | 2026-08-26 |
| node 22 · JS · npm · linux glibc · docker
Observations: PROJECT_TEST 1✓ — Verified: CONTRACT 1✓
|
LOW | 1 | 1 | 100% | 1 · 1✓ | 2026-09-07 |
| node 22.23 · JS · npm · linux glibc
Observations: PROJECT_PROCESS 2✓ — Verified: UNKNOWN 0✓ 6✕
|
ELEVATED FAILURE | 2 | 6 | 25% | 2 | 2026-08-31 |
snapshot · 2026-09-15
Failure clusters
-
observed PROJECT_PROCESS ERR_ASSERTION Evidence gap ×8 4.15.9 → 6.2.4 → 6.2.5 → 6.2.8 → 6.2.9 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-14 · Last seen: 2026-11-17Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×8 6.2.5 → 6.2.9 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:769e5b509341…node:internal/process/promises:<n> · triggerUncaughtException(err, true <path> fromPromise */); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×2 6.2.9 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:81715947e190…node:internal/process/promises:<n> · triggerUncaughtException(err, true <path> fromPromise */); · ^ …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 6.2.9 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:95724a8063ba…fil<path>:<n> · throw new TypeError(<str>); · ^ · TypeError: non-extractable CryptoKey cannot be exported as a JWKnode · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate