Records/npm/@esbuild/netbsd-arm64/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.

• 0.28.2 FAIL
• 0.28.1 PASS 1 passing observations
• 0.27.2 PASS 1 passing observations
• 0.25.12 FAIL

Where it reproduced

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

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 0.25.12 → first passing release 0.27.2

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

• Last passing release 0.28.1 → first failing release 0.28.2

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

Evidence gaps

• No failure domain was inferred for this failure.

Published answers for the affected releases

• @esbuild/netbsd-arm64 0.28.2 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-28
• @esbuild/netbsd-arm64 0.28.2 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
• @esbuild/netbsd-arm64 0.25.12 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-27