Weave Code
Rate Limit Bundle Laravel Package
fusonic/rate-limit-bundle
A Symfony bundle for declarative rate limiting. Apply attributes to controllers and services, configure limits and intervals, and use flexible storage backends to throttle APIs and protect actions with minimal setup and clean Symfony integration.
Simple rate limiting based on routes.
Frequently asked questions about Rate Limit Bundle
- Can I use fusonic/rate-limit-bundle in a Laravel application?
- No. It is a Symfony bundle built for Symfony's kernel, dependency injection container, routing metadata, and event system, not a Laravel package. Laravel has no bundle registration model and uses a different HTTP kernel and middleware pipeline. Use Laravel's native throttle middleware and RateLimiter::for() instead.
- Does fusonic/rate-limit-bundle support Laravel 10 or Laravel 11?
- No supported Laravel version exists. The last release was 2020-12-11 and targeted Symfony 5.x-era dependencies, and the repository is archived. Its Composer constraints are likely to conflict with PHP 8.2+ and Laravel 10-11 dependency graphs. Adoption in a Laravel codebase is not viable.
- How do I install fusonic/rate-limit-bundle?
- Historically it would be installed with Composer into a Symfony application, but the repository is archived and the last release was in 2020. For Laravel, installation is not applicable and composer require will often fail on constraint resolution. It should not be installed as part of a Laravel rate limiting implementation.
- What is the Laravel equivalent of fusonic/rate-limit-bundle?
- Laravel's native rate limiting stack is the equivalent: the throttle middleware, Illuminate Cache RateLimiter, and RateLimiter::for() configured in RouteServiceProvider or AppServiceProvider. It is first-party, declarative, and testable, and a basic limit can be applied with middleware('throttle:60,1'). There is no capability gap that this Symfony bundle closes in Laravel.
- Is fusonic/rate-limit-bundle maintained?
- No. The repository is archived, the last release was 2020-12-11, and it has zero stars and zero dependents. There is no security response path, no upgrade cadence, and no downstream community reporting issues. That makes it unsuitable for a security-relevant control such as rate limiting.
- Is it safe to use an archived rate limiting package in production?
- No. Rate limiting is a control-plane defence against brute-force attempts, credential stuffing, scraping, abuse, and cost overruns. Shipping an unmaintained component on that path creates a standing audit and incident-response liability. Use a maintained first-party implementation with a clear patching path.
- Can fusonic/rate-limit-bundle handle per-tenant or cost-weighted rate limits?
- It is a Symfony route-based limiter, and even in Symfony it is likely superseded by symfony/rate-limiter, which has shipped since 5.2. In Laravel, per-tenant keys and cost-weighted limits should be implemented with native RateLimiter::for() custom limiters. Bridging this archived Symfony bundle is not the right approach.
- Why does composer require fusonic/rate-limit-bundle fail in Laravel?
- The package comes from a 2020 Symfony 5.x-era release, so its Composer constraints collide with PHP 8.2+ and Laravel 10-11 dependency graphs. Constraint resolution often fails before any code is written. It would also pull in Symfony framework contracts that Laravel does not use in the same shape.
- What are the alternatives to fusonic/rate-limit-bundle for Laravel?
- Use Laravel's native throttle middleware and RateLimiter facade, backed by the cache or Redis store for distributed counters. If you need advanced patterns such as per-tenant keys or cost-weighted limits, build a first-party limiter with RateLimiter::for(). A Symfony bundle is not an appropriate alternative in a Laravel application.
- How do I test rate limiting in Laravel?
- Laravel's native rate limiting can be tested with its HTTP test helpers by configuring RateLimiter::for() for the test case and asserting 429 responses when limits are exceeded. The throttle middleware is declarative and works with the framework's testing facilities. This Symfony bundle does not apply to that workflow.
Weaver
How can I help you explore Laravel packages today?