Records/npm/semver/failure issue

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.

• 7.8.5 PASS 206 passing observations
• 7.8.0 PASS 1 passing observations
• 7.7.4 FAIL
• 7.7.3 PASS 1 passing observations
• 7.7.1 PASS 3 passing observations
• 7.5.3 PASS 1 passing observations

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×2 2026-08-29 → 2026-08-29

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 passing release 7.7.3 → first failing release 7.7.4

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

• Last failing release 7.7.4 → first passing release 7.8.0

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

Evidence gaps

• No resolved dependency tree for 7.8.0 or for 7.7.4, 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

• semver 7.7.4 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. HOW MIT-0 · 2026-08-21
• semver 7.7.4 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. HOW MIT-0 · 2026-08-20