Records/npm/jose/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 6.2.9 not measured
• 6.2.8 PASS 126 passing observations
• 6.2.5 PASS 8 passing observations
• 6.2.4 FAIL
• 6.1.2 not measured

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-09-15 → 2026-09-15

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.2.4 → first passing release 6.2.5

  Both trees resolved every dependency to the same version. Nothing here moved.

Evidence gaps

• Releases in this window never measured at PROJECT_COMPILE: 2
• No failure domain was inferred for this failure.

Published answers for the affected releases

• jose 6.2.4: SignJWT Built ? 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. HOWjose.SignJWT MIT-0 · 2026-09-06
• jose 6.2.4: compactVerify Built ? 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. HOWjose.compactVerify MIT-0 · 2026-09-04
• jose 6.2.4: CompactSign Built ? 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. HOWjose.CompactSignnode 22.23.2 MIT-0 · 2026-09-04