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 FAIL
• 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
• 6.3.1 FAIL
• 5.7.2 FAIL

Where it reproduced

• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×4 2026-08-25 → 2026-08-25
• executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×3 2026-08-21 → 2026-08-21
• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-08-26 → 2026-08-26
• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-18 → 2026-08-18
• executionContext=node · os=linux · runtime=node@22 ×1 2026-09-07 → 2026-09-07

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.5.3

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

• 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.

• Last passing release 7.8.0 → first failing release 7.8.5

  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.
• No resolved dependency tree for 7.5.3 or for 6.3.1, 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.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 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
• 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