Recordsnpmaggregate-errorfailure issue
Failure signature
PROJECT_TYPECHECK Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-21 · Last seen: 2026-08-21
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TYPECHECK 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=cjs · os=windows · runtime=node@24.13 ×1 2026-08-21 → 2026-08-21
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.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 5.0.0 | 3.1.0 |
|---|---|---|
| clean-stack | 5.3.0 | 2.2.0 |
| indent-string | 5.0.0 | 4.0.0 |
Moved: 2 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
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_TYPECHECK.
- Releases in this window never measured at PROJECT_TYPECHECK: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.