npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@klausrz/rate-limiter

v1.0.0

Published

Redis sliding window rate limiter for Express

Readme

@klausrz/rate-limiter

A Redis-backed sliding window rate limiter for Express. Uses optimistic locking (WATCH / MULTI / EXEC) for accurate, race-free request counting.

Install

npm install @klausrz/rate-limiter ioredis

Peer dependencies: ioredis >= 5 and express >= 4 must be installed in your project.

Usage

Express middleware

import express from "express";
import Redis from "ioredis";
import { rateLimiter } from "@klausrz/rate-limiter";

const app = express();
const redis = new Redis(); // connect to your Redis instance

app.use(
  rateLimiter({
    redis,
    windowMs: 60_000,   // 1-minute window
    maxRequest: 100,    // max 100 requests per window
    keyPrefix: "rl:",   // optional namespace
  })
);

The middleware automatically reads the client IP from X-Forwarded-For (first value) and falls back to req.socket.remoteAddress.

Response headers set on every request:

| Header | Description | |---|---| | X-RateLimit-Limit | Maximum requests allowed in the window | | X-RateLimit-Remaining | Requests remaining in the current window | | X-RateLimit-Reset | Unix timestamp (seconds) when the window resets | | Retry-After | Seconds until retry is allowed (only on 429 responses) |

When the limit is exceeded the middleware responds with HTTP 429:

{ "message": "Too many requests", "retryAfter": 42 }

Core function (framework-agnostic)

import Redis from "ioredis";
import { isAllowed } from "@klausrz/rate-limiter";

const redis = new Redis();

const result = await isAllowed("user-123", {
  redis,
  windowMs: 60_000,
  maxRequest: 10,
  keyPrefix: "rl:",
});

if (!result.allowed) {
  // result.remaining === 0
  // result.resetAtMs  — timestamp when the oldest request expires
}

API

rateLimiter(options) → Express middleware

isAllowed(identifier, options)Promise<RateLimiterResult>

RateLimiterOption

| Property | Type | Required | Description | |---|---|---|---| | redis | Redis | ✓ | ioredis client instance | | windowMs | number | ✓ | Sliding window length in ms | | maxRequest | number | ✓ | Max requests per window | | keyPrefix | string | | Optional Redis key prefix |

RateLimiterResult

| Property | Type | Description | |---|---|---| | allowed | boolean | Whether the request is permitted | | remaining | number | Requests remaining in the window | | resetAtMs | number | Timestamp (ms) when the window resets |

Algorithm

Uses a sorted set per identifier where each member is the request timestamp. On every call:

  1. Remove entries older than now - windowMs (evict stale)
  2. Add the current timestamp
  3. Check cardinality against maxRequest
  4. Set key TTL to windowMs for automatic cleanup

WATCH / MULTI / EXEC ensures correctness under concurrent requests. On transaction conflict the call retries for up to 2 seconds before failing open.

License

MIT