- What is saibal-roy/laravel-iam and what does it do?
- saibal-roy/laravel-iam is a Laravel package that aims to bring identity and access management concepts to Laravel applications. It provides a starting point for handling users, roles, and permissions, with a deliberately lightweight scope. Community adoption has been limited, and the repository is archived.
- Is saibal-roy/laravel-iam still maintained?
- No. The repository is archived and the last release was June 2020, with only about 12 stars, so there are no upstream fixes or active maintenance. Treat it as a reference implementation or a source of patterns rather than a current dependency.
- Which Laravel and PHP versions does laravel-iam support?
- The 2020 release date strongly suggests the package targets Laravel 6/7-era applications and pre-PHP 8.x stacks, but you must verify the actual Composer constraints. Check the supported Laravel and PHP versions, service-provider auto-discovery, and migration compatibility before attempting integration. Do not assume it installs cleanly on a modern stack.
- Can I install laravel-iam on Laravel 10 or Laravel 11?
- It is not a safe assumption that laravel-iam works with Laravel 10 or 11. Because the package is archived and dates from 2020, modern framework contracts and PHP 8.x requirements are likely to conflict. Run a time-boxed compatibility spike or fork and test it against your exact target versions before using it.
- How does laravel-iam integrate with Laravel Gates, Policies, and the User model?
- The package is positioned as a Laravel-native IAM layer that can work with Eloquent, middleware, Gates and Policies, and database-backed authorization. However, its exact role and permission resolution semantics and how they map to Laravel's Gate/Policy system need to be verified in code. Do not couple application code directly to its models or facade; use an internal authorization adapter instead.
- Does laravel-iam include migrations, seeders, caching, audit logging, or multi-tenancy?
- The documented scope is users, roles, and permissions, but the context does not confirm details such as teams, tenancy, permission inheritance, caching, audit logging, or seeders. Inspect the package's migrations, models, and service provider to confirm what schema and behavior it actually ships. Treat undocumented security assumptions as a review item.
- Is laravel-iam safe to use for production authorization?
- It is high risk for production IAM. The package is archived, has very low adoption, dates from 2020, and has unclear security assumptions and test coverage, while IAM code is security-sensitive. Do not adopt it without a fork, dependency updates, and a security review.
- Does laravel-iam have tests, and can I run them against my Laravel version?
- Test coverage is a stated technical risk for laravel-iam, and the context does not establish that the suite is complete or runnable on modern Laravel. You should inspect the tests and attempt to run them against your target Laravel and PHP versions during a time-boxed spike. If tests are missing or fail, budget for writing coverage in a fork.
- What are alternatives to laravel-iam for roles and permissions in Laravel?
- For modern Laravel applications, native Gates and Policies plus a maintained package such as spatie/laravel-permission or a custom domain model are usually safer baselines. laravel-iam is best treated as a reference implementation or prototype source, not as a production authorization foundation. Choose an alternative that has active maintenance and compatibility with your Laravel and PHP versions.
- How should I evaluate, migrate from, or fork laravel-iam?
- Start with a time-boxed spike behind an internal authorization interface or adapter so application code does not depend on the package's models or facade. Validate representative roles, permissions, policies, and your existing auth guard and user model. If the spike passes, fork the repository, pin the fork, add CI across supported Laravel/PHP versions, document ownership and patching, and perform a security review; otherwise extract requirements and migrate to native Laravel authorization or a maintained package.