CodeSampleX

Recordsnpmexpress-rate-limit8.6.1

Change the conditions
Fixed
Runtimenode 24 Package version8.6.1
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

express-rate-limit @8.6.1windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 50 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (5)

Project observations
142 / 177
Contract verifications
0 / 50
Usage records
444
Independent reporting peers
1
Failures with a captured fingerprint
7 / 35
Last recorded
2026-11-21

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 1

First observed break

8.6.1

windows · executionContext=node

19 FAIL · stage: PROJECT_TEST

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
ip-address 10.7.3 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
debug 4.4.3 PASS All observations passed contract passed 11 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

Showing the 12 most-reported of 52 recorded failure clusters. The rest are single reports.