# FuelPHP 1.x: a small PHP framework with a long-lived 1.x line > The fuel/fuel repository holds the 1.x line of FuelPHP, a fast and lightweight PHP framework at version 1.8.2, released under the MIT licence. The documentation is split between the release branch and the development branch, the project is maintained by a small named team with a pull-request culture, and the repository still carries a vendored Composer binary and a Travis configuration. **fuel/fuel** — Fuel PHP Framework v1.x is a simple, flexible, community driven PHP 5.3+ framework, based on the best ideas of other frameworks, with a fresh start! FuelPHP is now fully PHP 8.0 compatible. - Repository: https://github.com/fuel/fuel - Website: http://fuelphp.com - Stars: 1,502 · Forks: 295 - Language: PHP - License: MIT - Published: 2026-10-20 · Updated: 2026-10-20 · Language: en - Canonical page: https://hysenlabs.com/projects/fuel-fuel ## What this repository actually contains The fuel/fuel repository is the 1.x line of FuelPHP, and the branch name says so plainly, since the default branch is 1.8/master rather than main. The version at the top of the README is 1.8.2, and the framework is described as fast and lightweight, and as community driven, with the aim of keeping the good ideas of other frameworks and dropping their rougher edges. The project metadata places the description of the 1.x line as a simple and flexible framework for PHP, and the accompanying site links the release documentation, an API browser, the development branch documentation and a second API browser for that branch, plus a support forum for comments, discussion and community support. The licence is MIT, with the terms in a licence file in the repository root. So the repository is the release line of a mature but deliberately unfashionable framework, with the documentation written to serve two audiences at once. ## The PHP version statements disagree This is the first thing a reader should notice, and it is a small illustration of how a project description and its README can drift apart. The repository description calls the 1.x line a framework for PHP 5.3 and up and states that it is now fully compatible with PHP 8.0. The README body describes a framework for PHP 5.4 and up and says it is fully compatible with PHP 7.3. Both cannot be the current truth, and neither is stated as a deprecation notice, so a reader who takes either sentence at face value could end up targeting a runtime the code does not support. The reliable answer lives in the Composer manifest in the repository root, which is the file that declares the actual constraint, and a framework that offers two different compatibility claims in two places is a reasonable reason to check that file before writing any code. It is also a reminder that a repository description is a summary written for a listing page rather than a specification. ## Two documentation sets, and why the split exists The documentation structure is a good indicator of how a project is run. There is a set of release documentation and a release API browser for the code that is actually shipped, and a separate set for the development branch, which is where the documentation for unreleased work lives, and a development wiki on the project repository for the notes that do not fit in either. The pattern is conventional and useful. A user reads the release documentation and the release API browser, so the reference they follow matches the version they installed, while a contributor reads the development branch documentation, which is allowed to be ahead of the released code. The support forum is listed in the same block, with the explicit purpose of comments, discussion and community support, which tells you the project expects a good share of its questions to be answered in public and archived where they can be found later. ## The people, and how somebody joins the project The team section names two people in current roles, Harro Verton as project manager and developer, and Emlyn West as core developer working on the ORM, and then a longer alumni list, which includes Mark Saghi-Kazar as a developer, Frank de Jonge, Jelmer Schreuder, Phil Sturgeon and Dan Horrigan, who is listed as the founder and a developer. That last group is the interesting part for an engineer reading the repository in 2026, because several of those names are associated with work in other parts of the PHP ecosystem, and their presence tells you where the framework's ideas came from. The joining procedure is unusual enough to be worth quoting in spirit. You cannot apply for membership. You send pull requests, you work on outstanding feature requests or bugs, and you become active in the IRC channel, and the project says that if your skills are good enough you will be noticed and asked to join the team. ## The repository layout and the artefacts of its age The tree is small and tells you the shape of the thing. The fuel/ directory holds the framework itself, the oil file is the command line entry point that the project is known for, and the public/ directory is the document root that a web deployment would point at. The Composer manifest and a bundled Composer binary sit at the root, alongside a changelog, a contributing guide, a testing guide and the licence. Two files are worth pausing on, because they date the project precisely. The vendored composer.phar means the project expected to run on machines where installing Composer was awkward, a convention that has largely disappeared, and the Travis configuration in place of a GitHub Actions workflow places the continuous integration in the era before that was the default. Neither is a problem for a maintained 1.x line, but both are the reason a reader should check the changelog to see how actively the branch is worked on. ## Where the 1.x line stands, and what comes next The state of the repository is best described as quiet rather than abandoned. The last push was on 2026-09-15, so the branch is being touched, and the repository publishes no GitHub releases, which means the tags that matter are the ones on the project site rather than in the release list, and a reader who watches the repository rather than the site will see very little. The repository description refers to the 1.x line as having a fresh start, and the documentation links make the same distinction between the release line and the development branch, so the picture is of a stable 1.x that people still run, with the next generation being worked on elsewhere. For a team already on FuelPHP, that is a perfectly reasonable position. For a team choosing a framework today, the absence of a visible release trail in the repository, the mixed version statements and the age of the tooling are three reasons to look at the alternatives before committing a new build to this branch. ## FuelPHP 1.x next to a modern PHP framework The comparison that matters is with the frameworks a new PHP project would otherwise consider, and the difference in approach is clear. A modern framework brings a typed core, a maintained dependency set with security support, an active release train and a large ecosystem of first-party packages, and it brings a cost with it, a larger surface, a steeper learning curve and a bigger set of conventions to follow. FuelPHP 1.x goes the other way. It is small, it ships a command line tool, it keeps the API reference browsable, and it is maintained by a handful of people who have been doing it for years, which is a genuine advantage when you want to read the source of the framework you depend on. The trade is the one the changelog and the forum will tell you about, a branch that is worked on at a measured pace and a compatibility claim that has to be verified against the manifest rather than the prose. ## Conclusion FuelPHP 1.x fits a team that already runs it, that wants a framework without a heavy dependency tree, and that values a browsable API reference and a small maintainer community over a large ecosystem. It does not fit a new project that wants a modern PHP baseline, typed support and an active release train, because the version statements in this repository disagree and the 1.x line moves at a measured pace. Before adopting it, read composer.json for the real PHP constraint rather than the prose, and check the changelog and the forum to see whether the modules you need are still maintained, since a framework branch that is quiet is often quiet for a reason. ## FAQ ### What is FuelPHP 1.x? It is the 1.x line of FuelPHP, a fast and lightweight community driven PHP framework, at version 1.8.2, published under the MIT licence from the fuel/fuel repository. ### Which PHP versions does FuelPHP 1.x support? The README body describes a framework for PHP 5.4 and up with full PHP 7.3 compatibility, while the repository description claims PHP 5.3 and up and full PHP 8.0 compatibility, so the Composer manifest is the place to confirm the real constraint. ### Where is the FuelPHP documentation? There are release documentation and a release API browser for the shipped 1.x line, separate development branch documentation and an API browser for that branch, a development wiki on the project repository, and a support forum. ### How do I contribute to FuelPHP? You cannot apply for membership. The project asks for pull requests, work on outstanding feature requests or bugs, and activity in the IRC channel, and says that contributors with the right skills will be noticed and asked to join the team. ### What files are in the FuelPHP repository? The fuel/ directory with the framework, the oil command line entry point, the public/ document root, the Composer manifest and a bundled Composer binary, a Travis configuration, and the changelog, contributing, testing and licence files. ### Which licence is FuelPHP released under? The MIT licence, with the terms in the licence file at the repository root. ## Sources - [fuel/fuel on GitHub](https://github.com/fuel/fuel) - [Issues](https://github.com/fuel/fuel/issues) - [License: MIT](https://github.com/fuel/fuel/blob/1.8/master/LICENSE) - [Project website](http://fuelphp.com) - [README](https://github.com/fuel/fuel/blob/1.8/master/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/fuel-fuel