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

guardx-rate-limit

v0.3.1

Published

A lightweight and customizable Express rate limiting middleware.

Readme

GuardX 🚀

A lightweight, modular, and production-ready rate limiting middleware for Express.

GuardX provides a clean and stable API with built-in Memory and Redis stores. The Redis implementation uses atomic Lua scripting to ensure race-condition-free request counting under concurrent traffic.

📚 Documentation: https://guardx-official.vercel.app/


Installation

npm install guardx-rate-limit

For Redis support:

npm install redis

Quick Start

import express from "express";
import guardx from "guardx-rate-limit";

const app = express();

// Apply the rate limiter to all incoming requests
app.use(
    guardx({
        // Maximum number of requests allowed per window
        limit: 100,

        // Time window in milliseconds
        windowMs: 60 * 1000
    })
);

app.get("/", (req, res) => {
    res.json({
        success: true
    });
});

app.listen(3000);

Redis

import express from "express";
import { createClient } from "redis";
import guardx, { RedisStore } from "guardx-rate-limit";

const app = express();

// Create a Redis client
const client = createClient();

// Connect to Redis before using the limiter
await client.connect();

// Use Redis as the storage backend
app.use(
    guardx({
        // Maximum requests per time window
        limit: 100,

        // Window duration (1 minute)
        windowMs: 60 * 1000,

        // Use Redis instead of the default in-memory store
        store: new RedisStore(client)
    })
);

app.listen(3000);

The Redis store executes the Fixed Window algorithm using an atomic Lua script, combining Redis commands into a single operation for safe concurrent request counting.


Features

  • Fixed Window algorithm
  • Built-in Memory store
  • Redis store
  • Atomic Redis Lua implementation
  • Standard RateLimit-* headers
  • Retry-After header
  • Custom response handler
  • Lightweight and production-ready

Configuration

| Option | Type | Default | | ----------------- | --------------------------- | ---------------------- | | limit | number | 100 | | windowMs | number | 60000 | | message | string | "Too many requests." | | standardHeaders | boolean | true | | handler | function | undefined | | store | MemoryStore \| RedisStore | MemoryStore |


Custom Handler

guardx({
    // Override the default 429 response
    handler(req, res, info) {

        return res.status(429).json({
            success: false,
            message: "Rate limit exceeded",

            // Seconds until the client can make requests again
            retryAfter: info.retryAfter,

            // Remaining requests in the current window
            remaining: info.remaining,

            // Configured request limit
            limit: info.limit
        });

    }
});

Documentation

📚 Looking for advanced configuration, API reference, Redis setup, algorithms, and more? Visit the official documentation:

https://guardx-official.vercel.app/


License

MIT