- Can I use iampersistent/mongodb-acl-bundle in a Laravel application?
- Not directly. The package is a Symfony bundle that relies on Symfony's kernel, dependency injection, and security ACL conventions, and Laravel has no equivalent bundle boot path. Using it in Laravel would require building and maintaining a Symfony-Security-to-Laravel bridge, which is a significant architectural commitment rather than a normal Composer integration.
- Is iampersistent/mongodb-acl-bundle maintained?
- The package description states it is now maintained elsewhere, and the successor location is not legible from the metadata provided. It also has very low adoption, with 2 stars and 0 dependents reported in the evaluation. Treat this repository as historical reference unless you can independently confirm an actively maintained successor.
- What is iampersistent/mongodb-acl-bundle used for?
- It provides MongoDB-backed storage for Symfony's ACL/security model, persisting access control entries, resource identities, and permission rules in MongoDB. It is intended for applications that already use Symfony's ACL system and want permission data stored alongside document data. It is not a general-purpose Laravel authorization package.
- Does mongodb-acl-bundle support Laravel 10, 11, or 12?
- No. The package is built for Symfony's bundle and security ACL system, not Laravel's Gate and Policy authorization layer. There is no Laravel service provider, facade, or publishable configuration, so Laravel's package discovery will not make it work. Laravel version support is effectively out of scope for this package.
- How do I install iampersistent/mongodb-acl-bundle with Composer?
- You can require it with Composer, but installation alone does not make it usable in Laravel. In Symfony you would register the bundle and configure its services; Laravel does not consume Symfony bundles that way. For a Laravel app, a timeboxed install-and-boot spike is likely to confirm there is no working integration path.
- What PHP and MongoDB driver versions does mongodb-acl-bundle support?
- The package metadata does not document a clear compatibility envelope for modern PHP branches, ext-mongodb releases, or Doctrine MongoDB ODM major versions. Given its vintage, you should assume breakage on current runtimes until proven otherwise. Any evaluation should start with a short install-and-boot spike against your exact PHP and driver versions.
- Does it work with mongodb/laravel-mongodb or Eloquent?
- No. The package expects Symfony ACL persistence and likely Doctrine MongoDB ODM or the raw ext-mongodb extension, not Laravel's mongodb/laravel-mongodb Eloquent-style integration. The two stacks do not share models, connections, or lifecycle management. Laravel teams should not expect it to plug into existing Eloquent MongoDB models.
- What are the best alternatives for MongoDB-backed ACL in Laravel?
- Use mongodb/laravel-mongodb for persistence and keep authorization in Laravel-native tooling such as Gates, Policies, spatie/laravel-permission, or bouncer. If you truly need object-level ACL semantics, implement a thin, auditable policy layer that resolves permissions against MongoDB documents. That approach keeps the permission model bounded and team-owned instead of relying on an abandoned Symfony bundle.
- Is it safe to use mongodb-acl-bundle in production?
- The evaluation flags it as abandoned, with no issue triage, security response capability, or meaningful user base. Unmaintained authorization code is a security-sensitive surface, and fail-open permission bugs can be silent and high severity. For production, avoid it unless you vendor and pin a fork, add CI, and assign an explicit internal owner.
- How should I implement object-level permissions in Laravel with MongoDB?
- Start with Laravel Gates and Policies for role- and model-level checks, backed by mongodb/laravel-mongodb for storage. For row- or object-level rules that do not map cleanly to Gates, write a small policy layer that queries MongoDB documents and returns explicit allow or deny decisions. Keep that code tested, auditable, and owned by your team rather than adopting an unmaintained Symfony ACL bundle.