- What is Grafite Builder used for in Laravel?
- Grafite Builder is a rapid-development scaffolding toolkit for Laravel. You define models, forms, tables, pages, and APIs in simple YAML config files, and it generates the controllers, views, routes, and a basic admin panel. The goal was to ship full CRUD applications faster with less boilerplate during the Laravel 5.x era.
- Does Grafite Builder work with Laravel 10, 11, or 12?
- No. The package is archived with its last release on 2017-08-31 and its Composer constraints are pinned to illuminate/* 5.x and PHP 7.x. A composer require against Laravel 10, 11, or 12 will almost certainly fail on version constraints before any code executes. Even if you bypassed the constraints, the console API rewrite in Laravel 6+ and other breaking changes would surface fatal errors.
- Is grafite/builder still maintained?
- No. The repository is archived, there is no maintainer response channel, and there are zero dependents in the Composer ecosystem, meaning nobody is exercising the code against a modern framework. Star count (around 977 historically) is a lagging popularity signal, not a health signal. Abandonment risk here is realized rather than projected.
- How do I install Grafite Builder in a Laravel app?
- The conventional flow is composer require grafite/builder, then publish the config and assets via the service provider, then run the scaffolding commands against your YAML definitions. In practice this only works on a Laravel 5.5–5.8 / PHP 7.x stack, which is not a plausible target for new work. On a modern stack the install will not resolve, so treat any fork as an internal require-dev package rather than an upstream dependency.
- What Laravel and PHP versions does Grafite Builder support?
- It targets the Laravel 5.x and PHP 7.x era. Its generated stubs predate typed properties, constructor promotion, modern validation patterns, and current policy conventions. It is a dev-time scaffolding tool rather than a runtime library, which is the most important architectural fact about it.
- Can I use Grafite Builder safely in production?
- It is scaffolding, not a runtime dependency, so it should never ship in your production image. Confine it to a build or developer container and keep it in require-dev with production builds excluding it. That caps the blast radius, but it does not fix the stale generated output or the lack of a security disclosure channel.
- How is Grafite Builder different from php artisan make:* and published stubs?
- Its opportunity score of 1.84 reflects that there is little incremental value over native Artisan make commands combined with your own published stubs. Grafite Builder bundles a whole YAML-driven generation concept, but most of the practical value usually concentrates in one or two generators. The recommended path is to extract those specific stubs into your own package rather than adopting the whole toolkit.
- Is Grafite Builder a good alternative to Laravel Nova or other admin panel generators?
- Not for new work. It generates a basic admin panel from YAML definitions, but the output encodes 2017-era Laravel idioms and the package has no support or patching path. Nova and current admin tooling are actively maintained and integrate with modern Laravel conventions. Evaluate Grafite Builder as reading material and a source of extractable patterns, not as a competitor to maintained packages.
- How do I migrate or fork Grafite Builder for a modern Laravel codebase?
- Fork it, pin to a specific commit, and modernize the stubs to emit current Laravel output that is typed, PSR-12/Pint-clean, and includes test scaffolding. Consume the fork as an internal require-dev package and vendor it under your own namespace so Composer never resolves the upstream constraint. Note that the MIT license requires preserving the copyright notice in the fork.
- Does Grafite Builder work with PHP 8, and what breaks?
- Likely not without a rewrite. PHP 8.x will surface fatals from removed or renamed helpers, stricter type handling, and the Laravel 5.x to 6+ console signature changes. Facade alias registration is also a collision risk in apps that already define similarly named facades. Treat any PHP 8 compatibility as a porting project you own permanently, including future PHP major upgrades.