Weave Code
Acl Bundle Laravel Package
nuxia/acl-bundle
nuxia/acl-bundle is a lightweight ACL package for Laravel/PHP applications, providing role- and permission-based access control so you can protect routes, resources, and actions with configurable rules. It helps centralize authorization logic and keep application code clean.
Acl Bundle for Symfony 2
Frequently asked questions about Acl Bundle
- Is nuxia/acl-bundle a Laravel package?
- No. It is packaged as a Symfony 2 bundle, with a bundle class, dependency-injection extension, and service definitions rather than a Laravel service provider or facade. Laravel does not consume Symfony bundles, so using it would require an adapter layer or a port of its logic. Treat it as a Symfony artifact, not a Laravel dependency.
- Can I install nuxia/acl-bundle in a Laravel application with Composer?
- Composer may fetch the code, but there is no Laravel service provider, config publish tag, or facade to wire it into Laravel's container. Integration is really a port, not a configuration step, and would mean running a second DI paradigm alongside Illuminate. For most teams the correct decision is to reject it and pick a Laravel-native authorization package.
- How do I install nuxia/acl-bundle in a Symfony application?
- In a Symfony 2 application you would require it with Composer, register the bundle class in AppKernel, and configure its services through the bundle's extension. There is no documented Laravel install path. Because Symfony 2 is long past end of life, even the native install path targets an obsolete runtime.
- Does nuxia/acl-bundle support Laravel 10 or Laravel 11?
- There is no evidence of support for any Laravel version, including Laravel 10 and Laravel 11. The package carries Symfony bundle conventions and almost certainly depends on Symfony Security or Doctrine components. Modern Laravel authorization should use Gates, Policies, or a maintained Laravel-native ACL package instead.
- Which PHP and Symfony versions does nuxia/acl-bundle require?
- The repository metadata does not clearly disclose its PHP or Symfony version ranges, and Doctrine compatibility is also unknown. Given its Symfony 2 origins, the composer.json constraints are likely to conflict with current PHP runtimes. Check those constraints before any commitment, because they can hard-block a future upgrade cycle.
- How does the permission model in nuxia/acl-bundle work?
- The name does not disclose the underlying model, which could be ACL entries keyed to security identities, role hierarchies, or simple permission strings. It may wrap Symfony's legacy ACL component, which was deprecated upstream years ago, making the design obsolete regardless of code quality. Confirm whether it is an independent implementation and where permissions are persisted before evaluating further.
- Is nuxia/acl-bundle actively maintained?
- The repository shows two stars and zero dependents, with no visible CI badge, support policy, or issue activity. A package with no downstream consumers has rarely been exercised in production by anyone other than its author. Treat it as an unmaintained artifact and expect to own any code you adopt.
- What are the best alternatives to nuxia/acl-bundle for Laravel?
- For most Laravel applications, native Gates and Policies cover role and permission checks without extra dependencies. If you need a package, spatie/laravel-permission and bouncer are maintained options with real user bases and active maintainers. All three avoid the Symfony-to-Laravel translation work this bundle would require.
- Is nuxia/acl-bundle safe to use in production for authorization?
- Authorization is a trust boundary, and this package shows no security disclosure process, audit trail, or evidence of adversarial review. A defect in an ACL layer can fail open or fail closed silently, which is a serious production risk. Do not put it in a production authorization path without a funded audit and a clear owner.
- Can I use nuxia/acl-bundle to protect Laravel routes and actions?
- Not directly, because it ships no Laravel middleware, gate, or policy integration. Protecting routes would require extracting its domain logic into framework-agnostic classes and wrapping them behind your own Laravel middleware or Gate checks. That is a re-implementation you own, so budget for translation and testing work rather than configuration.
Weaver
How can I help you explore Laravel packages today?