Records/npm/semver/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_PROCESS 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 FAIL
• 7.8.0 not measured
• 7.7.4 PASS 34 passing observations
• 7.7.3 PASS 11 passing observations
• 7.7.1 not measured
• 7.5.3 not measured
• 6.3.1 FAIL
• 5.7.2 FAIL

Where it reproduced

• executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×18 2026-08-20 → 2026-08-29
• executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×11 2026-08-16 → 2026-08-16
• executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×6 2026-08-21 → 2026-08-26
• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×4 2026-08-18 → 2026-08-18
• executionContext=node · moduleSystem=esm · os=windows · runtime=node ×2 2026-08-16 → 2026-08-16
• executionContext=node · moduleSystem=cjs · os=windows · runtime=node ×1 2026-08-16 → 2026-08-16

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.3.1 → first passing release 7.7.3

  Releases between them never measured at this stage: 2

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

• Last passing release 7.7.4 → first failing release 7.8.5

  Releases between them never measured at this stage: 1

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

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_PROCESS: 3
• No failure domain was inferred for this failure.

Published answers for the affected releases

• semver 7.8.5 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. HOWnode 22.23.2 MIT-0 · 2026-08-21
• semver 7.8.5: eq, gt, gte 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. HOWeqgtgteltlteneqparsersortsortnode 22.22.2 MIT-0 · 2026-08-19
• semver 7.8.5: reverse sort semantic versions with semver.rsort 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. HOWrsortnode MIT-0 · 2026-08-19
• semver 6.3.1: parse 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. HOWsemver.parsenode 22.23.2 MIT-0 · 2026-08-28
• semver 6.3.1: minSatisfying 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. HOWsemver.minSatisfyingnode 22.23.2 MIT-0 · 2026-08-28
• semver 6.3.1: maxSatisfying 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. HOWsemver.maxSatisfyingnode 22.23.2 MIT-0 · 2026-08-28