CodeSampleX

Recordsnpmexpress-rate-limit8.7.1MemoryStore

Change the conditions
Fixed
SymbolMemoryStore Package managernpm
Filter OSdebian glibc Runtimenode 22 Package version8.7.1 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

MemoryStore @8.7.1debian glibc · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-10-21

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 1

First observed break

8.7.1

linux · node@22.23 · moduleSystem=esm · executionContext=node

1 FAIL · stage: PROJECT_TEST · fingerprint: sha256:ef96efaca8ddfbeeab2a7eea64a1b583e926d75644ef751cb70b035ace5efbd5

Library Version Health Measured there Projects
ip-address 10.7.4 CANDIDATE Correlated change; unproven combination contract passed 40 project-days
debug 4.4.3 PASS All observations passed contract passed 40 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: 1

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