Weave Code
Acl Bundle Laravel Package
short-edition/acl-bundle
A Laravel ACL package for role- and permission-based access control. Define roles and permissions, assign them to users, and protect routes, controllers, and UI elements with simple authorization checks that fit Laravel’s middleware and Gate patterns.
Symfony AclBundle
Frequently asked questions about Acl Bundle
- Is short-edition/acl-bundle a Laravel package or a Symfony bundle?
- Despite Laravel-oriented framing, the repository artifacts describe a Symfony bundle: it assumes a Symfony kernel, bundle registration, DI container compiler passes, and Doctrine entity mapping for its five ACL tables. Nothing in it maps onto Laravel's service-provider lifecycle or Eloquent. Confirm with the requester whether the real target is a Symfony service or a Laravel application before spending engineering time.
- Can I install short-edition/acl-bundle in a Laravel app with Composer?
- There is no supported Composer-level drop-in for Laravel. You would either bridge the bundle by hand-wiring its services inside a Laravel service provider alongside Doctrine, or port the ACL data model to Eloquent. Both paths produce bespoke code your team owns, with a realistic estimate of a multi-week spike for the bridge approach.
- Does short-edition/acl-bundle integrate with Laravel Gate and policies?
- No. The package does not touch Gate, Gate::before, policies, or Eloquent model hooks, which is exactly where Laravel authorization actually lives. Even a successful boot would leave your application with two parallel authorization systems and undefined precedence between them. That makes it unsuitable as an authorization layer for a Laravel codebase.
- Why is the Symfony ACL component considered deprecated?
- The underlying ACL component was deprecated in Symfony 3.4 and removed from the framework in Symfony 4.0. The platform vendor replaced it with voters and expression-based access control, which are simpler to reason about and cheaper to query. This bundle inherits a design the vendor itself retired, so you would be adopting a legacy model rather than a forward-looking one.
- What are better Laravel alternatives for roles and permissions?
- For most applications, Laravel's native Gates and Policies combined with a maintained roles-and-permissions package such as spatie/laravel-permission covers the requirement. Bouncer is another option if you need per-model abilities with a fluent API. All of these integrate with Gate checks, middleware, and Blade directives the way Laravel developers expect.
- Is short-edition/acl-bundle actively maintained and safe for production?
- The available signals are poor: zero stars, zero dependents, no visible maintainer activity, no release cadence, and no CI signal. There is no declared supported PHP or Symfony version range, no security disclosure process, and no advisory or CVE response path. That combination fails a standard third-party risk questionnaire outright.
- What are the performance concerns with ACL entry tables?
- ACL entry tables grow multiplicatively with objects times identities, so storage and query cost climb quickly in real applications. Mask resolution is expensive to query and difficult to index effectively. This is a known liability of the ACL model itself rather than a defect this fork could fix.
- Can I port the ACL data model to Eloquent and use it in Laravel?
- It is technically feasible to reimplement object identity, security identity, ACL entries, and permission masks on Eloquent and expose them through Gates. But that is a rewrite, not an integration: the package becomes a schema reference and provides no ongoing leverage. You would own and maintain the resulting code indefinitely.
- Do I need per-record ACL grants or just role-based checks?
- Most roadmaps need role-based checks, which Laravel already solves cleanly with Gates, Policies, and a roles-permissions package. True per-record ACL grants are only justified when individual records must have distinct grants per user or group. Clarify the required granularity before evaluating any ACL layer.
- Does short-edition/acl-bundle support Laravel 10 or 11 and which PHP versions?
- There is no declared Laravel support statement and no supported PHP or Symfony version range in the package metadata. Because it is a Symfony bundle rather than a Laravel package, Laravel version compatibility is effectively undefined. Do not assume it works with current Laravel releases without a scoped, timeboxed assessment.
Weaver
How can I help you explore Laravel packages today?