CodeSampleX

Recordsnpmexpress-rate-limit8.6.1express-rate-limit.rateLimit

Change the conditions
Fixed
OSubuntu glibc Package version8.6.1 Symbolexpress-rate-limit.rateLimit
Filter Runtimenode 22 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

express-rate-limit.rateLimit @8.6.1ubuntu glibc · x64 · node 22 · npm 10 · node

0 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 failed (2)

Project observations
3 / 3
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-08-31
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 1

First observed break

8.6.1

windows · executionContext=node

5 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
ip-address 10.3.1 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
ip-address 10.5.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
debug 4.4.3 PASS All observations passed contract passed 9 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.

Library8.7.08.6.28.6.1
ip-address 10.7.2 10.7.0 10.5.0
debug 4.4.3 4.4.3 4.4.3

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