Recordsnpm@oxc-project/typesfailure issue
Failure signature
PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-14 · Last seen: 2026-08-14
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.
- 0.149.0 PASS 16 passing observations
- 0.148.0 PASS 20 passing observations
- 0.147.0 PASS 22 passing observations
- 0.144.0 FAIL
- 0.142.0 PASS 1 passing observations
- 0.139.0 PASS 2 passing observations
- 0.137.0 not measured
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-14 → 2026-08-14
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 0.142.0 → first failing release 0.144.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release 0.144.0 → first passing release 0.147.0
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.
- Releases in this window never measured at PROJECT_PROCESS: 1
- No resolved dependency tree for 0.142.0 or for 0.144.0, 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
No published sample names these releases.