PHPackages                             luissobrinho/builder - 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. [Utility & Helpers](/categories/utility)
4. /
5. luissobrinho/builder

ActiveLibrary[Utility & Helpers](/categories/utility)

luissobrinho/builder
====================

Prepare your Laravel apps incredibly fast, with various commands, services, facades and boilerplates.

v0.0.11(5y ago)129[11 issues](https://github.com/luissobrinho/builder/issues)MITPHPPHP >=7.3

Since May 16Pushed 5y ago1 watchersCompare

[ Source](https://github.com/luissobrinho/builder)[ Packagist](https://packagist.org/packages/luissobrinho/builder)[ RSS](/packages/luissobrinho-builder/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (10)Dependencies (7)Versions (14)Used By (0)

Luissobrinho Builder
====================

[](#luissobrinho-builder)

**Builder** - A handful of tools for Rapid Laravel Development

[![Latest Version](https://camo.githubusercontent.com/bb540ec49394bc24a3fbab76cc8edc2a6558317caf5458f14a306e157781b3ae/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f762f6c756973736f6272696e686f2f6275696c6465722e737667)](https://packagist.org/packages/luissobrinho/builder)[![Build Status](https://camo.githubusercontent.com/7aeb73cdb4592a1bb72d3726b1f8bb605ecaa80698e47774b8d622431bd22022/68747470733a2f2f7472617669732d63692e6f72672f6c756973736f6272696e686f2f6275696c6465722e7376673f6272616e63683d646576656c6f70)](https://travis-ci.org/Luissobrinho/Builder)[![Packagist](https://camo.githubusercontent.com/65db618be413797fd66b12aa0480d4c439f9222f4b9867c25677a69f35f0a40c/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f64742f6c756973736f6272696e686f2f6275696c6465722e737667)](https://packagist.org/packages/luissobrinho/builder)[![license](https://camo.githubusercontent.com/850eae1099d2b05f53383473d7cd51f9bc1ab09b7d0d9e5122f1dd930efdcc6d/68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f6c6963656e73652f6d6173686170652f6170697374617475732e737667)](https://packagist.org/packages/luissobrinho/builder)

This is a set of tools to help speed up development of Laravel apps. You can start an app with various parts prewritten (Users, User Meta, Roles, Teams). And it comes with a powerful FormMaker which can generate form content from tables, and objects. It can generate epic CRUD prototypes rapidly with full testing scripts prepared for you, requiring very little editing. It also provides an elegant Cryptography tool which is URL friendly. Finally it brings along some friends with LaravelCollective as a vendor.

##### Author(s):

[](#authors)

- [Luis Eduardo Altino](https://github.com/luissobrinho) ()

General Requirements
--------------------

[](#general-requirements)

1. PHP 7.3+
2. OpenSSL
3. JSON

Compatibility and Support
-------------------------

[](#compatibility-and-support)

Laravel VersionPackage TagSupported6.x - 7.x0.0.11yesInstallation
------------

[](#installation)

Start a new Laravel project:

```
laravel new {project_name}

```

or

```
composer create-project laravel/laravel {project_name}

```

Then run the following to add the Luissobrinho Builder

```
composer require "luissobrinho/builder"

```

Time to publish those assets! Luissobrinho Builder uses LCrud and LForm which have publishable assets.

```
php artisan vendor:publish

```

or

```
php artisan vendor:publish --provider="Luissobrinho\LCrud\LCrudProvider"

```

You now have Luissobrinho Builder installed. Try out the *Starter Kit*.

### Application Starter Kit

[](#application-starter-kit)

!!! warning "Make sure you followed the getting started instructions!"

Luissobrinho Builder provides an elegant solution for starting an application by building the most basic views, controllers, models and migrations for your application. No need to use the `php artisan make:auth` because now you can easily start your whole application with this single command.

!!! tip "BUT, before we do that let's get a few things set up."

In order to make use of the starter kit you will need to modify some files. Check out the modifications below:

Alter the following to your `app/Providers/RouteServiceProvider.php` in the const `HOME`.

```
public const HOME = '/dashboard';
```

Add the following to your `app/Http/Kernel.php` in the `$routeMiddleware` array.

```
'admin' => \App\Http\Middleware\Admin::class,
'permissions' => \App\Http\Middleware\Permissions::class,
'roles' => \App\Http\Middleware\Roles::class,
'active' => \App\Http\Middleware\Active::class,

```

If you don't want to worry about email activation then remove this from the route's middleware array:

```
'active'

```

Add the following to 'app/Providers/AuthServiceProvider.php' in the boot method

```
Gate::define('admin', function ($user) {
    return ($user->roles->first()->name === 'admin');
});

Gate::define('team-member', function ($user, $team) {
    return ($user->teams->find($team->id));
});
```

Add the following to 'app/Providers/EventServiceProvider.php' in the $listen property

```
 \App\Events\UserRegisteredEmail::class => [
    \App\Listeners\UserRegisteredEmailListener::class,
],
```

### Regarding Email Activation

[](#regarding-email-activation)

The Starter kit has an email activation component added to the app to ensure your users have validated their email address. You can disable it by removing the `active` middleware from the `web` routes. You will also have to disable the Notification but it won't cause any problems if you remove the email activation.

You will also need to set the location of the email for password reminders. (config/auth.php - at the bottom)

```
'passwords' => [
    'users' => [
        'provider' => 'users',
        'email' => 'emails.password',
        'table' => 'password_resets',
        'expire' => 60,
        'throttle' => 60,
    ],
],
```

#### Things to note

[](#things-to-note)

You may try and start quickly by testing the registration but please make sure your app's email is configured or it will throw an exception. You can do this in the `.env` file easily by setting it to 'log' temporarily

```
MAIL_DRIVER=log
```

#### Last Steps

[](#last-steps)

Once you've added in all these parts you will want to run the starter command!

```
php artisan luissobrinho:starter
```

Then you'll have to refresh the list of all classes that need to be included in the project.

```
composer dump-autoload
```

Then you'll need to migrate to add in the users, user meta, roles and teams tables. The seeding is run to set the initial roles for your application.

```
php artisan migrate --seed
```

Once you get the starter kit running you can register and login to your app. You can then you can visit the settings section of the app and set your role to admin to take full control of the app.

### What Starter Publishes

[](#what-starter-publishes)

#### Controllers

[](#controllers)

Luissobrinho Builder updated the basic controllers to handle things like creating a profile when a user is registered, as well as setting default return routes to `dashboard` etc. It also provides contollers for handling profile modifications and pages, team management etc. The admin controller handles the admin of users, modifying a user provided the user has the admin role.

- app/Http/Controllers/
    - Admin/
        - DashboardController.php
        - UserController.php
        - RoleController.php
    - Auth/
        - ActivateController.php
        - ForgotPasswordController.php
        - LoginController.php
        - RegisterController.php
        - ResetPasswordController.php
    - User/
        - PasswordController.php
        - SettingsController.php
    - PagesController.php
    - TeamController.php

#### Middleware

[](#middleware)

Luissobrinho Builder overwrites the default middleware due to changes in the redirects. It also provides the `Admin` middleware for route level protection relative to roles.

- app/Http/Middleware/
    - Active.php
    - Admin.php
    - Permissions.php
    - RedirectIfAuthenticated.php
    - Roles.php

#### Requests

[](#requests)

There are requests provided for handling the creation of Teams and updating of all components. Here we integrate the rules required that are able to run the validations and return errors. (If you're using Luissobrinho Builder FormMaker Facade then it will even handling accepting the errors and highlighting the appropriate fields.)

- app/Http/Requests/
    - PasswordUpdateRequest.php
    - RoleCreateRequest.php
    - TeamCreateRequest.php
    - TeamUpdateRequest.php
    - UserInviteRequest.php
    - UserUpdateRequest.php

#### Routes

[](#routes)

Given that there are numerous routes added to handle teams, profiles, password etc all routes are overwritten with the starter kit.

- routes/web.php

#### Config

[](#config)

The permissions config file is published, this is a way for you to set access levels and types of permissions `Roles` can have

- config/permissions.php

#### Events

[](#events)

The events for various actions.

- app/Events/
    - UserRegisteredEmail.php

#### Listeners

[](#listeners)

The event listeners for various actions.

- app/Listeners/
    - UserRegisteredEmailListener.php

#### Models

[](#models)

Models are obvious, but when we then integrate Services below which handle all the buisness logic etc which make the calls to the models we implement SOLID practices, the Controller, Console or other Service, which calls the service only accesses the model through it. Once these have been integrated please ensure you delete the `User.php` model file and ensure that you have followed the installation and config instructions.

- app/Models/
    - UserMeta.php
    - User.php
    - Team.php
    - Role.php

#### Notifications

[](#notifications)

These are all our emails that we need to send out to the users in the application. These are amazing since they use the power of Laravel's notifcation component.

- app/Notficiations/
    - ActivateUserEmail.php
    - NewAccountEmail.php
    - ResetPasswordEmail.php

#### Services

[](#services)

Service structure allows us to keep the buisness logic outside of the models, and controllers. This approach is best suited for apps that may wish to integrate an API down the road or other things. It also allows for a highly testable structure to the application.

- app/Services/
    - Traits/
        - HasRoles.php
        - HasTeams.php
    - ActivateService.php
    - RoleService.php
    - TeamService.php
    - UserService.php

#### Database

[](#database)

Please ensure that all migrations and seeds are run post installation. These seeds set the default roles available in your application.

- database/factories/
    - RoleFactory.php
    - TeamFactory.php
    - UserFactory.php
    - UserMetaFactory.php
- database/migrations/
    - 2015\_11\_30\_191713\_create\_user\_meta\_table.php
    - 2015\_11\_30\_215038\_create\_roles\_table.php
    - 2015\_11\_30\_215040\_create\_role\_user\_table.php
    - 2015\_12\_04\_155900\_create\_teams\_table.php
    - 2015\_12\_04\_155900\_create\_teams\_users\_table.php
- database/seeds/
    - DatabaseSeeder.php
    - RolesTableSeeder.php
    - UserTableSeeder.php

#### Views

[](#views)

The views consist of as little HTML as possible to perform the logical actions. These are intended to be the most basic, and all of which are intended to be modified.

- resources/views/
    - admin/
        - roles/
            - edit.blade.php
            - index.blade.php
            - invite.blade.php
        - users/
            - edit.blade.php
            - index.blade.php
            - invite.blade.php
        - dashboard.blade.php
    - auth/
        - activate/
            - email.blade.php
            - token.blade.php
        - passwords/
            - email.blade.php
            - reset.blade.php
        - login.blade.php
        - register.blade.php
    - errors/
        - 401.blade.php
        - 404.blade.php
        - 503.blade.php
    - partials/
        - errors.blade.php
        - message.blade.php
        - status.blade.php
    - team/
        - create.blade.php
        - edit.blade.php
        - index.blade.php
        - show.blade.php
    - user/
        - meta.blade.php
        - password.blade.php
        - settings.blade.php
    - dashboard.blade.php

#### Tests

[](#tests)

Luissobrinho Builder starter kit provides the basic unit tests for each of its own parts. This provides some great examples of testing for building an application quickly.

- tests/
    - Feature/
        - TeamIntegrationTest.php
    - Unit/
        - UserServiceTest.php
        - TeamServiceTest.php
        - RoleServiceTest.php

After Setup
-----------

[](#after-setup)

### Dashboard access

[](#dashboard-access)

The application dashboard is found by browsing to the /dashboard endpoint. The default admin user login credentials are:

- email:
- password: admin

### User

[](#user)

The user model is expanded with Luissobrinho Builder Starter Kit. It adds to the basic user model: roles, teams, and user meta. The relationships are as follows:

- Meta: hasOne
- Roles: belongsToMany
- Team: belongsToMany

It also provides the following methods:

```
meta() // The relationship method
roles() // The relationship method
hasRole(role_name) // checks if user has role
teams() // The relationship method
isTeamMember(team_id) // checks if user is member
isTeamAdmin(team_id) // checks if user is admin level member

```

### Middleware

[](#middleware-1)

#### Admin

[](#admin)

The Admin middleware acts as a tool for setting admin level permissions on the routes or controller level.

```
['middleware' => 'admin']

```

This simple addition to a route will ensure the user has access to the admin level, if not it will return them from where they came.

#### Active

[](#active)

The Active middleware acts checks if the account as been activated by accessing the activate url with the emailed token.

```
['middleware' => 'active']

```

This simple addition to a route will ensure the user has an activated account, if not it will redirect them to the /active page so they can request another activation token if necessary.

#### Roles

[](#roles)

The Roles middleware allows you to set custom roles for your routes.

```
['middleware' => 'roles:admin|member']

```

#### Permissions

[](#permissions)

The Permissions middleware allows you to set custom permissions (a subset of roles) for your routes

```
['middleware' => 'permissions:admin|somethingDescriptive']

```

You can set permissions in the `config/permissions.php`

### Bootstrap UI

[](#bootstrap-ui)

!!! Tip "Bootstrap Version 4"

If you feel like opting in for the Application starter kit. You also have a great bootstrapping option for the views. You can blast through the initial building of an app and hit the ground running!

> You can use [LCrud](https://github.com/luissobrinho/lcrud) to create magical CRUDs for Laravel

```
php artisan luissobrinho:bootstrap

```

!!! Tip "This will also ensure that your webpack file is prepared to run"

#### What Boostrap Publishes

[](#what-boostrap-publishes)

The command will overwrite any existing files with the bootstrap version of them:

- resources/views/
    - user/
        - meta.blade.php
        - password.blade.php
        - settings.blade.php
    - admin/
        - users/
            - edit.blade.php
            - index.blade.php
            - invite.blade.php
    - auth/
        - login.blade.php
        - password.blade.php
        - register.blade.php
        - reset.blade.php
    - dashboard/
        - main.blade.php
        - panel.blade.php
    - emails/
        - new-user.blade.php
        - password.blade.php
    - errors/
        - 404.blade.php
        - 503.blade.php
    - partials/
        - errors.blade.php
        - message.blade.php
    - team/
        - create.blade.php
        - edit.blade.php
        - index.blade.php
        - show.blade.php

### Application Activities

[](#application-activities)

Sometimes its handy to know what your users are up to when they browse your site or application. The Activity kit gives you everything you need to track your users and their every action. The middleware does most of it for you, but your welcome to customize it to fit your needs.

#### Setup

[](#setup)

```
php artisan luissobrinho:activity
```

Add to your `config/app.php` the following:

```
App\Providers\ActivityServiceProvider::class,
```

##### Facades

[](#facades)

Provides the following tool for in app features:

```
Activity::log($description);
Activity::getByUser($userId);
```

##### Helper

[](#helper)

```
activity($description) // will log the activity
```

### Application Features

[](#application-features)

Sometimes what we need is a simple way to toggle parts of an app on and off, or hey, maybe the client wants it. Either way, using the feature management kit can take care of all that. Now you or your clients can toggle signups on an off, or any other features in the app. Just utilize the blade or helper components to take full control of your app.

#### Setup

[](#setup-1)

```
php artisan luissobrinho:features
```

You may want to add this line to your navigation:

```
 Features
```

Add to your `config/app.php` the following:

```
App\Providers\FeatureServiceProvider::class,
```

Add this to the `app/Providers/RouteServiceProvider.php` in the `mapWebRoutes(Router $router)` function:

```
require base_path('routes/features.php');
```

##### Facades

[](#facades-1)

Provides the following tool for in app features:

```
Features::isActive($key);
```

##### Blade

[](#blade)

```
@feature($key)
// code goes here
@endfeature
```

##### Helper

[](#helper-1)

```
feature($key) // will return true|false
```

##### What Features Publishes:

[](#what-features-publishes)

The command will overwrite any existing files with the features version of them:

- app/Facades/Features.php
- app/Http/Controllers/Admin/FeatureController.php
- app/Http/Requests/FeatureCreateRequest.php
- app/Http/Requests/FeatureUpdateRequest.php
- app/Models/Feature.php
- app/Providers/FeatureServiceProvider.php
- app/Services/FeatureService.php
- database/migrations/2016\_04\_14\_210036\_create\_features\_table.php
- resources/views/admin/features/create.blade.php
- resources/views/admin/features/edit.blade.php
- resources/views/admin/features/index.blade.php
- routes/features.php
- tests/Feature/FeatureIntegrationTest.php
- tests/Unit/FeatureServiceTest.php

### Application Logs

[](#application-logs)

The logs tool simply add a view of the app logs to your admin panel. This can be of assistance durring development or in keeping an application in check.

#### Setup

[](#setup-2)

```
php artisan luissobrinho:logs
```

You may want to add this line to your navigation:

```
 Logs
```

Add this to the `app/Providers/RouteServiceProvider.php` in the `mapWebRoutes(Router $router)` function:

```
require base_path('routes/logs.php');
```

### Application Notifications

[](#application-notifications)

Luissobrinho Builder's notifications will build a basic controller, service, and views for both users and admins so you can easily notifiy your users, in bulk or specifically.

##### Setup

[](#setup-3)

```
php artisan luissobrinho:notifications
```

You may want to add this line to your navigation:

```
 Notifications
 Notifications
```

Add this to the `app/Providers/RouteServiceProvider.php` in the `mapWebRoutes(Router $router)` function:

```
require base_path('routes/notification.php');
```

##### Facades

[](#facades-2)

Provides the following tool for in app notifications:

```
Notifications::notify($userId, $flag, $title, $details);
```

Flags can be any bootstrap alert: default, info, success, warning, danger

##### What Notifications Publishes:

[](#what-notifications-publishes)

The command will overwrite any existing files with the notification version of them:

- app/Facades/Notifications.php
- app/Http/Controllers/Admin/NotificationController.php
- app/Http/Controllers/User/NotificationController.php
- app/Http/Requests/NotificationRequest.php
- app/Models/Notification.php
- app/Services/NotificationService.php
- database/migrations/2016\_04\_14\_180036\_create\_notifications\_table.php
- resources/views/admin/notifications/create.blade.php
- resources/views/admin/notifications/edit.blade.php
- resources/views/admin/notifications/index.blade.php
- resources/views/notifications/index.blade.php
- resources/views/notifications/show.blade.php
- routes/notification.php
- tests/NotificationIntegrationTest.php
- tests/NotificationServiceTest.php

### Forge Integration

[](#forge-integration)

The FORGE component provides you with access to the FORGE API in your admin panel. Rather than having to log into FORGE for each adjustment, now you can simply log into your own application and in the admin panel adjust the scheduler, or workers on your server configuration.

##### Requires

[](#requires)

```
composer require themsaid/forge-sdk
```

##### Setup

[](#setup-4)

```
php artisan luissobrinho:forge
```

You may want to add this line to your navigation:

```
 Forge Settings
 Forge Calendar
 Forge Workers
```

Add this to the `app/Providers/RouteServiceProvider.php` in the `mapWebRoutes(Router $router)` function:

You will see a line like: `->group(base_path('routes/web.php'));`

You need to change it to resemble this:

```
->group(function () {
    require base_path('routes/web.php');
    require base_path('routes/forge.php');
}
```

Add these to the .env:

```
FORGE_TOKEN=
FORGE_SERVER_ID=
FORGE_SITE_ID=
```

### Application API

[](#application-api)

If you feel like opting in for the Laracogs starter kit. You can also easily build in an API layer. Running the `luissobrinho:api` command will set up the bare bones components, but you can also use the API tools as a part of the CRUD now by using the `--api` option.

##### Requires

[](#requires-1)

```
composer require tymon/jwt-auth
```

##### Setup

[](#setup-5)

```
php artisan luissobrinho:api

```

Essentially you want to do all the basic setup for JWT such as everything in here: Then follow the directions regarding installation on:

Add this to the `app/Providers/RouteServiceProvider.php` file in the `mapWebRoutes(Router $router)` function:

```
require base_path('routes/api.php');
```

Add to the app/Http/Kernal.php under routeMiddleware:

```
'jwt.auth' => \Tymon\JWTAuth\Middleware\GetUserFromToken::class,
'jwt.refresh' => \Tymon\JWTAuth\Middleware\RefreshToken::class,
```

Add to except attribute the app/Http/Middleware/VerifyCsrfToken.php (You also have to do this for CRUDs you add):

```
'api/v1/login',
'api/v1/user/profile',
```

If you use Apache add this to the .htaccess file:

```
RewriteEngine On
RewriteCond %{HTTP:Authorization} ^(.*)
RewriteRule .* - [e=HTTP_AUTHORIZATION:%1]
```

Also update your jwt config file and set the user to:

```
\App\Models\User::class
```

##### What API publishes

[](#what-api-publishes)

The command will overwrite any existing files with the api version of them:

- app/Http/Controllers/Api/AuthController.php
- app/Http/Controllers/Api/UserController.php
- routes/api.php

### Application Queue

[](#application-queue)

Horizon is amazing if you've got a redis instance configured and are running your queue through that, but not all apps need that nor do that have to start there. If you've got a database driven queue and are looking for an easy management component to handle job retrying and cancellations then this will be a perfect addition to your app.

##### Setup

[](#setup-6)

```
php artisan luissobrinho:queue
```

Add this to the `app/Providers/RouteServiceProvider.php` in the `mapWebRoutes(Router $router)` function:

```
require base_path('routes/queue.php');
```

You may want to add this line to your navigation:

```
 Queue
```

### Social Media Logins

[](#social-media-logins)

If you're looking to offer social media logins on your application and want a simple way to get started then look no further. Simply run the command and follow the steps below and you'll have GitHub login out of the box. Integrating Facebook etc afterward is easy when you look at the code base.

##### Requires

[](#requires-2)

```
composer require laravel/socialite
```

##### Setup

[](#setup-7)

```
php artisan luissobrinho:socialite

```

The next step is to prepare your app with socialite:

Add this to your app config under providers:

```
Laravel\Socialite\SocialiteServiceProvider::class
```

Add this to your app config under aliases:

```
'Socialite' => Laravel\Socialite\Facades\Socialite::class,
```

Add `require base_path('routes/socialite.php');` to the `app/Providers/RouteServiceProvider.php` in the `mapWebRoutes(Router $router)` function:

```
Route::middleware('web')
    ->namespace($this->namespace)
    ->group(function () {
        require base_path('routes/socialite.php');
        require base_path('routes/web.php');
    });
```

Finally set the access details in the services config:

```
'github' => [
    'client_id' => 'id code',
    'client_secret' => 'secret code',
    'redirect' => 'http://your-domain/auth/github/callback',
    'scopes' => ['user:email'],
],
```

### Auditing

[](#auditing)

This package will help you understand changes in your Eloquent models, by providing information about possible discrepancies and anomalies that could indicate business concerns or suspect activities.

##### Requires

[](#requires-3)

```
composer require owen-it/laravel-auditing
```

Essentially you want to do all the basic setup for Laravel Auditing such as everything in here: Then follow the directions regarding installation on:

##### Setup

[](#setup-8)

```
php artisan luissobrinho:auditing

```

##### What Auditing publishes

[](#what-auditing-publishes)

The command will overwrite any existing files with the auditing version of them:

- resources/lcrud/Model.txt
- app/Listeners/AuditedListener.php
- app/Listeners/AuditingListener.php

### Debugbar

[](#debugbar)

This is a package to integrate the debugging bar for Laravel. You can publish assets and configure it through Laravel. Even when the bar is disabled in `APP_DEBUG = false` it is possible to enable it using the "Dev" permission placed by the Start package.

##### Requires

[](#requires-4)

```
composer require barryvdh/laravel-debugbar --dev
```

Essentially you want to do all the basic setup for Laravel Debugbar such as everything in here: Then follow the directions regarding installation on:

##### Setup

[](#setup-9)

```
php artisan luissobrinho:debugbar

```

Insert the Middleware in the Kernel.php file of the $ middlewareGroups variable in the web index

```
protected $middlewareGroups = [
    'web' => [
        // ...
        \App\Http\Middleware\DebugMiddleware::class
    ],

    'api' => [
        // ...
    ]
];
```

###### Optional

[](#optional)

Disable laravel debugging by changing the value of the `APP_DEBUG` variable to false in the `.env` file

```
APP_DEBUG=false
```

##### What DebugBar publishes

[](#what-debugbar-publishes)

The command will overwrite any existing files with the debugbar version of them:

- app/Http/Middleware/DebugMiddleware.php

---

License
-------

[](#license)

Luissobrinho Builder is open-sourced software licensed under the [MIT license](http://opensource.org/licenses/MIT)

### Bug Reporting and Feature Requests

[](#bug-reporting-and-feature-requests)

Please add as many details as possible regarding submission of issues and feature requests

### Disclaimer

[](#disclaimer)

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

###  Health Score

18

—

LowBetter than 8% of packages

Maintenance0

Infrequent updates — may be unmaintained

Popularity9

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity48

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% 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 ~2 days

Total

11

Last Release

2170d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/b895f8c44bd74d8ad19241803acb2f5763db593c608314de8ec07700e79796eb?d=identicon)[luissobrinho](/maintainers/luissobrinho)

---

Top Contributors

[![luissobrinho](https://avatars.githubusercontent.com/u/17295212?v=4)](https://github.com/luissobrinho "luissobrinho (41 commits)")

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/luissobrinho-builder/health.svg)

```
[![Health](https://phpackages.com/badges/luissobrinho-builder/health.svg)](https://phpackages.com/packages/luissobrinho-builder)
```

###  Alternatives

[codefog/contao-haste

haste extension for Contao Open Source CMS

42650.8k139](/packages/codefog-contao-haste)[eliashaeussler/typo3-form-consent

Extension for TYPO3 CMS that adds double opt-in functionality to EXT:form

1481.0k](/packages/eliashaeussler-typo3-form-consent)[ronasit/laravel-helpers

Provided helpers function and some helper class.

1475.7k13](/packages/ronasit-laravel-helpers)[numero2/contao-storelocator

Contao Plugin for managing stores (or in common address data) and providing a frontend-search based on geo data

121.5k](/packages/numero2-contao-storelocator)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)