Recordsnpmlru-cachefailure issue
Failure signature
PROJECT_TEST ELIFECYCLE Evidence gap ×10
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-18 · Last seen: 2026-09-07
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 11.5.2 PASS 3 passing observations
- 11.5.1 not measured
- 11.2.4 PASS 1 passing observations
- 10.4.3 FAIL
- 7.18.3 FAIL
- 6.0.0 FAIL
- 5.1.1 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×4 2026-08-21 → 2026-08-21
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-08-25 → 2026-08-25
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-08-26 → 2026-08-26
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-08-18 → 2026-08-18
- executionContext=node · os=linux · runtime=node@22 ×1 2026-09-07 → 2026-09-07
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 failing release 10.4.3 → first passing release 11.2.4
Both trees resolved every dependency to the same version. Nothing here moved.
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.
Moved: 1 · 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.
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- lru-cache 10.4.3: LRUCache 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. HOWlru-cache.LRUCachenode 22.23.2 MIT-0 · 2026-08-23
- lru-cache 10.4.3 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-21
- lru-cache 10.4.3 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-20
- lru-cache 7.18.3 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-21
- lru-cache 7.18.3: Basic LRUCache get set and TTL eviction 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. HOWLRUCachenode 22.23.2 MIT-0 · 2026-08-19
- lru-cache 6.0.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-21