Recordsnpmlru-cache6.0.0
Change the conditions
Current conditions
lru-cache @6.0.0ubuntu glibc · x64 · node 22 · npm 10 · node
package-level total, not an API
0 of 4 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (3)
- Project observations
- 28 / 28
- Contract verifications
- 0 / 4
- Usage records
- 3
- Independent reporting peers
- 3
- Last recorded
- 2026-09-07
Dependency Health
Observed combinations and failure evidence for this release
First observed break
6.0.0
windows · node@24.13 · moduleSystem=esm · executionContext=node
62 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| yallist | 4.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 27 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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.
Recent failure clusters
-
observed PROJECT_TEST ELIFECYCLE Evidence gap ×10 5.1.1 → 6.0.0 → 7.18.3 → 10.4.3 executionContext=nodeEvidence quality: legacy-evidence-incomplete · Environment variants: 5 · First recorded: 2026-08-18 · Last seen: 2026-09-07Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×10 5.1.1 → 6.0.0 → 7.18.3 → 11.5.2 executionContext=node sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-08-30 · Last seen: 2026-09-16Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×3 6.0.0 → 7.18.3 → 10.4.3 executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 sha256:795cbb5ee086…Error: Cannot find module <str> · Require stack: · - <path> · - <path>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 6.0.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:0d62cac8c07a…AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · + actual - expected · + <str> · - <str>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 6.0.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:e1d65fc7c136…<path>:<n> · throw new Error(`Unsupported arch ${name}`) · ^ · Error: Unsupported arch 1node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×1 6.0.0 executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 sha256:9e0be0092066…Contract test failure: AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · <str> !== null · at testAll (<url>) · at <url>node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-31 · Last seen: 2026-08-31Diagnostic re-verification candidate