Recordsnpmjosefailure issue
Failure signature
PROJECT_TEST Evidence gap ×3
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-11-21 · Last seen: 2026-11-21
jose.JWTVerifyGetKey jose.SignJWT jose.createLocalJWKSet jose.createRemoteJWKSet jose.exportJWK jose.generateKeyPair jose.jwtVerify
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 6.2.15 FAIL
- 6.2.13 PASS 17 passing observations
- 6.2.12 PASS 1 passing observations
- 6.2.10 not measured
- 6.2.8 PASS 169 passing observations
- 6.2.5 PASS 52 passing observations
- 6.2.4 PASS 17 passing observations
- 6.1.2 FAIL
- 4.15.9 not measured
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-11-21 → 2026-11-21
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-11-21 → 2026-11-21
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release 6.1.2 → first passing release 6.2.4
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release 6.2.13 → first failing release 6.2.15
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- Releases in this window never measured at PROJECT_TEST: 2
- No resolved dependency tree for 6.2.13 or for 6.2.15, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.