- What is Grafite CrudMaker for Laravel?
- Grafite CrudMaker is a generation-time Artisan tool that reads a YAML or JSON schema and scaffolds Laravel CRUD: migrations, Eloquent models, controllers, routes, Blade views, and tests. It is not runtime admin CRUD; it emits plain Laravel code that you own. The repository is archived and targets Laravel 5.x-era conventions.
- How do I install grafite/crudmaker?
- Install it with Composer in a Laravel 5.5 through 5.8-era application, then run the crud:make Artisan command against your YAML schema. You can publish and edit the stubs to match your conventions. Modern Laravel installs will likely hit Illuminate and Symfony constraint conflicts, so treat it as a fork or port candidate rather than a drop-in package.
- Does Grafite CrudMaker support Laravel 10 or Laravel 11?
- Not out of the box. Its stubs and dependencies are designed around Laravel 5.5 through 5.8 and PHP 7.x, and the archived repository will not ship compatibility updates. Running it on Laravel 10 or 11 requires rewriting stubs, replacing removed helper functions, and updating Blade and Faker APIs. Budget a port assessment before relying on it for modern applications.
- Is grafite/crudmaker still maintained?
- No. The repository is archived, so upstream will never ship security or compatibility patches, and there is no CVE feed to subscribe to. The zero-dependents signal may reflect old Laravel package-discovery behavior, but the practical maintenance status is abandoned. If you adopt it, you own the fork, the patch SLA, and any security review.
- How do I test CRUD generated by Grafite CrudMaker?
- Generate one representative CRUD module in a throwaway Laravel app and run the emitted tests, then diff the output against your existing module conventions. The generator can emit tests, but you must verify that generated migrations, routes, controllers, and views actually run on your target Laravel version. Treat generated code like hand-written code and code-review it during a low-risk pilot.
- Can I customize Grafite CrudMaker templates and stubs?
- Yes. CrudMaker generates from published stubs, so you can edit templates to match your house conventions before generating modules. This is the main reusable part, but template drift is a risk because regenerated code can diverge from hand-edited code with no reconciliation story. Encode your standards in the stubs before a second team touches the tool.
- Does Grafite CrudMaker work with PHP 8?
- Not reliably as-is. The designed target is PHP 7.x with Laravel 5.x-era stubs, so PHP 8 compatibility must be verified by generating a representative module and running it. Watch for removed global helpers, Symfony Console constraints, and Faker signature changes. Every mismatch is a silent-failure vector in a generator because the output can look plausible but fail at runtime.
- Should I use Grafite CrudMaker in production?
- Only with caution and code review. It is a generation-time tool, not a runtime dependency, so the generated artifacts are plain Laravel code you own outright. However, naive runs often produce controllers without authorization policies or FormRequest validation, and generated migrations can collide with existing schema. Treat the output like hand-written code and review it before deployment.
- How does Grafite CrudMaker handle validation and authorization?
- It does not reliably add them by default. Generated controllers frequently ship without authorization policies or FormRequest validation, so a naive run can produce insecure CRUD. You must add validation and authorization yourself or rewrite the stubs to emit your standards. This is a key reason to pilot the generator on one low-risk internal admin module first.
- What are alternatives to Grafite CrudMaker?
- The realistic options are forking and porting CrudMaker, running it in an isolated generator service and copying output into your monolith, or mining its schema grammar and stub structure for an in-house Laravel generator. A thin in-house generator that emits FormRequests, policies, API resources, and Pest tests avoids owning abandoned code. The schema format is the reusable asset; the stubs are the liability.