PHPackages                             ifirlana/laravel-pkg - 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 &amp; Helpers](/categories/utility)
4. /
5. ifirlana/laravel-pkg

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

ifirlana/laravel-pkg
====================

firlana boilerplate template

00PHPCI failing

Since Jan 16Pushed 6y ago1 watchersCompare

[ Source](https://github.com/ikhlas-firlana/laravel-pkg)[ Packagist](https://packagist.org/packages/ifirlana/laravel-pkg)[ RSS](/packages/ifirlana-laravel-pkg/feed)WikiDiscussions master Synced today

READMEChangelogDependenciesVersions (1)Used By (0)

laravel-pkg
===========

[](#laravel-pkg)

template package from

Thanks bro

Boilerplate Laravel 5 Package
=============================

[](#boilerplate-laravel-5-package)

Installation
------------

[](#installation)

Clone this repo with minimal history:

```
git clone --depth 1 git@github.com:cviebrock/laravel5-package-template.git
```

Rename the directory and re-init it as your own package:

```
mv laravel5-package-template my-package
cd my-package
rm -rf .git
git init
```

Configuration
-------------

[](#configuration)

The boilerplate files provide a scaffold for building your own package. You'll need to make a bunch of changes to the files we've provided to make it your own.

### composer.json

[](#composerjson)

Edit `composer.json` to reflect your package information. At a minimum, you will need to change the package name and autoload lines so that "vendor/package" reflects your new package's name and namespace.

```
{
    "name": "vendor/package",
    ...
    "autoload": {
        "psr-4": {
            "Vendor\\Package\\": "src/"
        }
    },
    ...
},
```

### config/packagename.php

[](#configpackagenamephp)

Rename `config/packagename.php` to something more useful, like `config/my-package.php`. This is the configuration file that Laravel will publish into it's `config` directory. Laravel 5 doesn't use the `config/packages/vendor/...` structure that Laravel 4 did, so pick a file name that's not likely to conflict with existing configuration files.

### src/ServiceProvider.php

[](#srcserviceproviderphp)

Open up `src/ServiceProvider.php` as well. At a minimum you'll need to change the namespace at the top of the file (it needs to match the PSR-4 namespace you set in `composer.json`).

In the `boot()` method, comment out or uncomment the components your package will need. For example, if your package only has a configuration, then you can comment out everything except the `handleConfigs()` call:

```
public function boot() {
    $this->handleConfigs();
    // $this->handleMigrations();
    // $this->handleViews();
    // $this->handleTranslations();
    // $this->handleRoutes();
}
```

In the `handleConfigs()` method, you'll want to change the "packagename" references to the name you chose up above (in the \[config/packagename.php\] instructions).

For the other methods, again change instances of "vendor" and "packagename" to your package's name.

### Last Steps

[](#last-steps)

Update the `LICENSE` file as required (make sure it matches what you said your package's license is in `composer.json`).

Finally, edit this `README.md` file and replace it with a description of your own, awesome Laravel 5 package.

Commit everything to your (newly initialized) git repo, and push it wherever you'll keep your package (Github, etc.).

Enjoy coding!

###  Health Score

16

—

LowBetter than 5% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity0

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity34

Early-stage or recently created project

 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.

### Community

Maintainers

![](https://www.gravatar.com/avatar/0b92c24949f3eb9ce0894aacb7af5657691bd9d48f348231c59a10551be16729?d=identicon)[ifirlana](/maintainers/ifirlana)

---

Top Contributors

[![ikhlas-firlana](https://avatars.githubusercontent.com/u/37413806?v=4)](https://github.com/ikhlas-firlana "ikhlas-firlana (5 commits)")

---

Tags

laravellearningpackagepackagenamephp

### Embed Badge

![Health badge](/badges/ifirlana-laravel-pkg/health.svg)

```
[![Health](https://phpackages.com/badges/ifirlana-laravel-pkg/health.svg)](https://phpackages.com/packages/ifirlana-laravel-pkg)
```

PHPackages © 2026

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