Recordsnpmast-typesfailure issue
Failure signature
PROJECT_PROCESS ERR_ASSERTION Evidence gap ×7
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-18 · Last seen: 2026-08-26
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.
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×4 2026-08-18 → 2026-08-18
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×3 2026-08-26 → 2026-08-26
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.
- No release in this window recorded a passing observation at PROJECT_PROCESS.
- Releases in this window never measured at PROJECT_PROCESS: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- ast-types 0.13.4: AST traversal and transformation with visit and namedTypes check 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. HOWast-types.buildersast-types.namedTypesast-types.visitnode 22.23.2 MIT-0 · 2026-08-23