PHPackages vsch/user-privilege-mapper - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Authentication & Authorization](/categories/authentication) 4. / 5. vsch/user-privilege-mapper ActiveLibrary[Authentication & Authorization](/categories/authentication) vsch/user-privilege-mapper ========================== A Laravel Service Provider to handle testing of available user security privileges independent of User Model implementation 2.0.5(10y ago)38.0kMITPHPPHP >=5.4.0 Since Jul 21Pushed 10y ago1 watchersCompare [ Source](https://github.com/vsch/user-privilege-mapper)[ Packagist](https://packagist.org/packages/vsch/user-privilege-mapper)[ RSS](/packages/vsch-user-privilege-mapper/feed)WikiDiscussions master Synced 1mo ago READMEChangelogDependencies (1)Versions (19)Used By (0) Laravel User Privilege Mapper ============================= [](#laravel-user-privilege-mapper) This package implements a simple Service Provider that enables mapping of user privileges independent of the implementation of the User model. It uses Laravel macros() to create an interface between a user privilege test and the actual implementation of the code to check whether the current user has this privilege enabled. I use this package to allow my other packages to test for security privileges without having to dictate how the user model is defined within a project. For Laravel 4 use the Laravel4 branch, or require: `"vsch/user-privilege-mapper": "~1.0"` For Laravel 5 use the master branch, or require: `"vsch/user-privilege-mapper": "~2.0"` Installation ------------ [](#installation) 1. Require this package in your composer.json and run composer update (or run `composer require vsch/user-privilege-mapper:*` directly): ``` "vsch/user-privilege-mapper": "~2.0" ``` 2. After updating composer, add the ServiceProviders to the providers array in config/app.php ``` Vsch\UserPrivilegeMapper\UserPrivilegeMapperServiceProvider::class, ``` 3. add the Facade to the aliases array in config/app.php: ``` 'UserCan' => Vsch\UserPrivilegeMapper\Facade\Privilege::class, ``` 4. To create a mapping layer between your User model implementation and the need to test user privileges without knowing the implementation. You need to create named privileges for the UserPrivilegeMapper via the Laravel macro mechanism. This should be done in the initialization files. A good place is the `app/Providers/AppServiceProvider.php` file, add the following to the `boot()` function, if your User model has is\_admin and is\_editor attributes to identify users that have Admin and Editor privileges or just `return true` in both cases, if you don't have any way of determining user privileges: ``` \UserCan::macro("admin", function () { return ($user = Auth::user()) && $user->is_admin; }); \UserCan::macro("edit", function () { return ($user = Auth::user()) && ($user->is_admin || $user->is_editor); }); ``` 5. Testing whether a privilege is available is as simple as: ``` if (\UserCan::admin()) { // user has admin privileges } elseif (\UserCan::edit()) { // user has edit privileges } ``` If a macro was not previously defined then the privilege test will return false. Effectively, if the macro is not implemented then the privilege is treated as not existent for every user. The implementation is more of a convention that is implemented by Laravel's Macroable trait. I don't see this package changing unless I get an epiphany. So consider this package code complete. However, suggestions are appreciated and welcome. :) ### Health Score 33 — LowBetter than 75% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity22 Limited adoption so far Community9 Small or concentrated contributor base Maturity67 Established project with proven stability Bus Factor1 Top contributor holds 90% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~14 days Recently: every ~51 days Total 16 Last Release 3747d ago Major Versions 1.0.10 → 2.0.12015-07-24 ### Community Maintainers ![](https://www.gravatar.com/avatar/da34202063c0ece614c192a4aaa5b66ad8561d8e9e0f2b9bfbcabf03e55c0819?d=identicon)[vsch](/maintainers/vsch) --- Top Contributors [![vsch](https://avatars.githubusercontent.com/u/10299086?v=4)](https://github.com/vsch "vsch (18 commits)")[![killtw](https://avatars.githubusercontent.com/u/1076225?v=4)](https://github.com/killtw "killtw (2 commits)") --- Tags laravelauthAuthentication ### Embed Badge ![Health badge](/badges/vsch-user-privilege-mapper/health.svg) ``` [![Health](https://phpackages.com/badges/vsch-user-privilege-mapper/health.svg)](https://phpackages.com/packages/vsch-user-privilege-mapper) ``` ### Alternatives [tymon/jwt-auth JSON Web Token Authentication for Laravel and Lumen 11.5k49.1M350](/packages/tymon-jwt-auth)[php-open-source-saver/jwt-auth JSON Web Token Authentication for Laravel and Lumen 8359.8M53](/packages/php-open-source-saver-jwt-auth)[auth0/login Auth0 Laravel SDK. Straight-forward and tested methods for implementing authentication, and accessing Auth0's Management API endpoints. 2745.0M3](/packages/auth0-login)[vinkas/firebase-auth-laravel Firebase Authentication package for Laravel PHP Framework 392.1k](/packages/vinkas-firebase-auth-laravel) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)