Recordsnpmip-addressfailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×9
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-14 · Last seen: 2026-08-29
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.
- 10.7.0 PASS 56 passing observations
- 10.5.0 FAIL
- 10.4.0 PASS 17 passing observations
- 10.3.1 PASS 23 passing observations
- 10.1.0 PASS 4 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×6 2026-08-14 → 2026-08-18
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×2 2026-08-29 → 2026-08-29
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-21 → 2026-08-21
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 10.4.0 → first failing release 10.5.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release 10.5.0 → first passing release 10.7.0
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.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- ip-address 10.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. HOW MIT-0 · 2026-08-23