Recordsnpmipaddr.jsfailure issue
Failure signature
PROCESS_START process start failed Evidence gap ×4
Evidence quality: partial · structured-termination · gap diagnostic-missing · First recorded: 2026-09-13 · Last seen: 2026-09-16
sha256:c12549970456…
ipaddr.js.IPv6 ipaddr.js.isValid ipaddr.js.parse ipaddr.js.process
Where it was measured
PASS means the release recorded a passing observation at PROCESS_START and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-09-13 → 2026-09-13
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-09-16 → 2026-09-16
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: diagnostic-missing.
- No release in this window recorded a passing observation at PROCESS_START.
- Releases in this window never measured at PROCESS_START: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- ipaddr.js 2.5.0 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-09-13
- ipaddr.js 1.9.1 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-20