Laravel Ban
A Laravel package that simplifies blocking and banning Eloquent models with support for multiple bans, soft deletes, and middleware.
What is Laravel Ban?
Laravel Ban is a Laravel package that provides a simple and elegant way to add banning functionality to Eloquent models. It solves the problem of managing user or model bans in Laravel applications by offering features like temporary bans, ban history, route protection middleware, and event-driven integrations. It extends beyond just users, allowing any Eloquent model to be bannable.
Laravel developers building applications that require user moderation, access control, or content restriction features, such as forums, admin panels, or community platforms.
Developers choose Laravel Ban because it integrates seamlessly with Laravel's ecosystem, uses traits for easy implementation, supports complex ban scenarios (like multiple bans and expirations), and includes ready-to-use middleware and events, reducing custom code and maintenance overhead.
Overview
Laravel Ban simplify blocking and banning Eloquent models.
Use Cases
Best For
- Adding user banning functionality to Laravel applications
- Implementing moderation systems for community platforms or forums
- Restricting access to certain routes for banned users
- Managing temporary bans with automatic expiration
- Keeping an audit trail of ban history for compliance
- Extending ban capabilities to non-user models like teams or organizations
Not Ideal For
- Projects not using Laravel's Eloquent ORM or requiring database migrations
- Applications needing in-memory or session-based banning without persistent records
- Teams seeking a zero-configuration, drop-in banning solution without middleware or event systems
Pros & Cons
Pros
Supports many bans per model, enabling detailed moderation history and complex scenarios like repeated offenses.
Keeps removed bans as soft-deleted records, preserving compliance-friendly history without data loss.
Includes middleware to block or automatically log out banned users on protected routes, reducing custom access control code.
Works with any Eloquent model, such as Teams or Organizations, not just Users, extending banning capabilities broadly.
Cons
Tightly coupled with Laravel's ecosystem, making it unsuitable for non-Laravel projects or custom ORMs, leading to vendor lock-in.
Requires adding database columns and traits to models, which adds initial configuration steps compared to simpler flag-based approaches.
Ban checks rely on database queries and scopes, potentially increasing query load in high-traffic applications with extensive ban records.
Frequently Asked Questions
Related Projects
LiveWireA full-stack framework for Laravel that takes the pain out of building dynamic UIs.
Debug BarDebugbar for Laravel (Integrates PHP Debug Bar)
IDE HelperIDE Helper for Laravel
Intervention ImagePHP Image Processing
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.