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 🙏

© 2024 – Pkg Stats / Ryan Hefner

cattleguard

v2.0.0

Published

Rate limiting stampede protection for express.

Downloads

153

Readme

Cattleguard

Greenkeeper badge

Build Status Coverage Status

An express middleware for rate limiting an application to provide stampede protection.

Usage

const cattleguard = require('cattleguard');
const redis = require('redis');

const rClient = redis.createClient();

// Cattleguard now expects the `set` method to include a ttl value. If your
// store does not accept this value by default you will need to wrap your store
// with a method that performs both the set and expire.
// For example:
const client = {
  get(...args) {
    rClient.get(...args);
  },
  set(key, val, ttl, cb) {
    rClient.set(key, val, (err) => {
      if (err) {
        return cb(err);
      }

      rClient.expire(ttl, cb);
    })
  }
}

const config = {
 total: 300,
 expire: 1000,
 onRateLimited: (req, res, next) => {
    res.status(503).send('Service Unavailable');
 }
};

// Rate limiting for _all_ routes.
app.use(cattleguard(config, client));

// Rate limiting for a single route.
config.perRoute = true;
app.post('/blogs', cattleguard(config, client), (req, res, next) => {
  // ...
});

// Rate limiting for a subset of routes based on method.
config.perMethod = true;
app.route('/blogs')
  .all(cattleguard(config, client))
  .post((req, res, next) => {
    // Will have its own rate limit.
  })
  .get((req, res, next) => {
    // Will have its own rate limit.
  });

// Rate limiting based on request criteriea.
config.lookup = (req) => req.headers['x-forwarded-for'];
app.post('/blogs', cattleguard(config, client), (req, res, next) => {
  // ...
});

Configuration options

  • config - Rate limit configuration, contains:
    • total: integer, the number of requests per a time period to allow before rate limiting.
    • expire: integer, the time period in milliseconds to limit requests.
    • onRateLimited: function, the method to execute when a rate limit has been reached. Accepts:
      • req: The reequest object.
      • res: The response object.
      • next: The method to execute after the on rate limited method, if needed.
    • perRoute: boolean, true if rate limiting should happen per route. default: false
    • perMethod: boolean, true if rate limiting should happen per HTTP method. default: false
    • lookup: function, used to return an identifier for the user requesting. This will have the effect of creating a per-user rate limit. default: undefined
  • store - A store to maintain the rate limit counts in. Must provide get and set methods with the following signatures:
    • get: gets a value from the store.
      • key - The key for the rate limit information.
      • callback - A callback to execute after getting, parameters are err and limit where limit is the value for the key.
    • set: sets a value in the store.
      • key - The key for the rate limit information.
      • value - The value to store.
      • ttl - The timeout in seconds for the rate limit information.
      • callback - A callback to execute after setting, parameters are err.

Credits

This module was heavily influenced by express-limiter but allows application rate limiting in the interest of guarding against backend failures, rather than the consumer only rate limiting approach that express-limiter takes.