Recordsnpmexpress-rate-limit8.6.1
Change the conditions
Current conditions
express-rate-limit @8.6.1windows 11 · x64 · node (version not recorded) · npm · node
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (5)
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-13
Dependency Health
Observed combinations and failure evidence for this release
First observed break
8.6.1
windows · executionContext=node
5 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 |
| 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.
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
-
observed PROJECT_TEST Evidence gap ×5 8.6.1 → 8.6.2 executionContext=node · os=windowsEvidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-21 · Last seen: 2026-08-25Diagnostic re-verification candidate