PHPackages blackskyliner/leaugefw - 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. [Framework](/categories/framework) 4. / 5. blackskyliner/leaugefw AbandonedArchivedLibrary[Framework](/categories/framework) blackskyliner/leaugefw ====================== PHP Framework based on ThePHPLeauge Packages/Components 11PHP Since Mar 30Pushed 10y ago1 watchersCompare [ Source](https://github.com/Blackskyliner/leaugefw)[ Packagist](https://packagist.org/packages/blackskyliner/leaugefw)[ RSS](/packages/blackskyliner-leaugefw/feed)WikiDiscussions master Synced 3w ago READMEChangelogDependenciesVersions (1)Used By (0) \#LeagueFw This little framework is all about using ThePHPLeague components where possible. It adds some compatibility or accessibility layers around them as needed. The whole framework is intended for small to middle sized applications. Where possible it will using correct type hinting and the framework also tries to be explicit about almost everything. The Frameworks intend is to only use automatic dependency resolving and not injecting the Container directly into Services. This is not a hard-limit but bridge components of the framework will be built with this in mind. There will be an Interface for every compatibility layer of the LeaugeFw. If possible the PSR Interfaces are used. So it should be easy to make the whole think compatible with almost every Framework out there. The DI Container can also be reconfigured within the Bootstrap process. In fact the supplied Bootstrap is not really needed. It will just ease the usage, as it just initializes some core components from ThePHPLeauge. Requirements ------------ [](#requirements) The only requirement, beside the composer stuff, is PHP7 as I won't look back at old stuff. It may run on 5.5+, I guess. Maybe I will setup some tests soon and get this checked... Structure --------- [](#structure) There are no by-convention and everything must be configured to be usable. However there are some recommendations: - `app/` contains the whole application code. `examples/` shows an possible directory setup. - `lib/` will be moved into its own Composer package later on. - `public/` is the facing part of the application and only this one should be accessible from the web. - `var/` holds all generated cache data and/or dynamic configuration data, like yml or ini configurations. The benefit of using this structure is that it's almost instantly compatible with some 3rd party tools. The `app/Resources/` and `public/` structure makes the configuration and usage of `laravel-elixir` a breeze. Some modern PHP applications also store their configuration and cache within a `var/` folder, so it's easier to find those data when searching through the application folders. Why another framework and not ? ------------------------------- [](#why-another-framework-and-not-) It's not about "Whoohoo, I created another, in my opinion super easy, super fast or super duper configurable micro framework!!!!!!11!1 Lets Microbenchmark it!1!11" Its all about the "No Framework" approach, like described [in this repository here](https://github.com/PatrickLouys/no-framework-tutorial). Composer makes it somewhat easy and I though why not as many components from one namespace as possible? So I just wanted to hack something together just to get used to all the processes and maybe to use it in some small private projects. I also feel that some frameworks just suck for me, because you'll need some 'idehelper.php' to get proper hinting in your favorite IDE. Some others have the problem that they are too "global" for me, I am not a fan of this facades stuff introduced by laravel. I just like real proper Container DI, with autowiring, which however must be configured explicitly first. No magic involved please! Because we all know, magic must be cached and magic sometimes get out of hand. ### Health Score 19 — LowBetter than 9% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity3 Limited adoption so far Community7 Small or concentrated contributor base Maturity41 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. ### Community Maintainers ![](https://avatars.githubusercontent.com/u/1038517?v=4)[Christoph Landsdorf](/maintainers/Blackskyliner)[@Blackskyliner](https://github.com/Blackskyliner) --- Top Contributors [![Blackskyliner](https://avatars.githubusercontent.com/u/1038517?v=4)](https://github.com/Blackskyliner "Blackskyliner (9 commits)") ### Embed Badge ![Health badge](/badges/blackskyliner-leaugefw/health.svg) ``` [![Health](https://phpackages.com/badges/blackskyliner-leaugefw/health.svg)](https://phpackages.com/packages/blackskyliner-leaugefw) ``` ### Alternatives [laravel/socialite Laravel wrapper around OAuth 1 & OAuth 2 libraries. 5.7k104.3M836](/packages/laravel-socialite)[laravel/dusk Laravel Dusk provides simple end-to-end testing and browser automation. 1.9k38.6M289](/packages/laravel-dusk)[nineinchnick/edatatables Grid widget for the Yii Framework, wrapper for the DataTables jQuery plugin 173.2k](/packages/nineinchnick-edatatables)[link-cloud/fast-hyperf LinkCloud Fast Hyperf 241.2k1](/packages/link-cloud-fast-hyperf) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)