Function throttling via the token-bucket algorithm

A straightforward token bucket implementation with no entanglements

A simple hierarchical token bucket

Limit the execution rate of a function using the token bucket algorithm

Token-bucket rate limiting middleware for WS-Kit

Rate limiting: token-bucket / fixed-window / sliding-window algorithms, deny list, sharding, pluggable stores, and procedure middleware

Rate limit plugin (concurrency + token bucket) for http-guardian.

Distributed rate limiting for @fonderiejs — atomic token bucket over memory, PostgreSQL, or Redis, with standard RateLimit-* headers.

IP based token bucket rate limiter / throttler.

Rate limiting plugin for NestJS RedisX with multiple algorithms (fixed-window, sliding-window, token-bucket)

Pluggable rate-limiting middleware for Express — token bucket & sliding window, in-memory or Redis-backed.

A basic token bucket that throttles based on key. Not only does it have a total bucket size, but also contains "child" buckets to prevent a single event from overwhelming the bucket.

A flexible rate limiter using different variations of the Token Bucket algorithm, with hierarchy support, and optional persistence in Redis. Useful for limiting API requests, or other tasks that need to be throttled.

This package provides a simple and efficient implementation of the token bucket algorithm for rate limiting. It helps you control the frequency of actions (such as API requests) within a specified time frame.

Enterprise security features — API key and JWT authentication, RBAC, token bucket rate limiting, audit logging with SIEM export

In-memory token bucket & leaky bucket rate limiter for Node APIs & frontend UI actions.

Multi-dimensional token-bucket / leaky-bucket rate limiter (per-tenant, per-provider, per-tool)

Token bucket rate limiting middleware for Express, per client

Rate-limiting plugin — per-endpoint, per-subject and per-tenant request limits via the RPC interceptors. Highly configurable rules (fixed-window / sliding-window / token-bucket), composite keying, static per-tenant overrides and a dynamic resolve() hook.

Layer-1 managed outbound-fetch / polite-crawl HTTP client. A domain-agnostic wrapper any ingestion/monitor/scraper calls instead of bare `fetch`: per-host token-bucket rate limiting, exponential backoff+jitter with Retry-After, a per-host circuit breaker,