- Does yab/crudmaker work with Laravel 10, 11, or 12?
- The repository is archived, so its Composer constraints are frozen at whatever Laravel and PHP versions were current when it was archived. Against a modern Laravel target, expect constraint conflicts, deprecated facade or service provider patterns, and illuminate/* pins that may no longer resolve. Check composer.json for the actual permitted versions and budget a short compatibility spike before committing.
- How do I install yab/crudmaker?
- It is a standard Composer install: require the package, register the service provider, and use the Artisan entry point with a config or definition file per entity. Because the package is archived, pin the exact version you test against rather than relying on a floating constraint. Confirm the service provider registration style matches your Laravel version's conventions.
- What does CrudMaker actually generate?
- It emits migrations, Eloquent models, resourceful controllers, routes, and Blade views from a declarative definition. Generation is a one-time accelerator, and the output is conventional resourceful MVC by design. Inspect generated code for validation rules, form requests, authorization policies, pagination, and eager loading, since it may only cover the happy-path skeleton.
- Does CrudMaker overwrite files I have already edited?
- Collision and diff handling is not documented, so treat regeneration as a risk until you test it yourself. Check whether the generator overwrites, skips, or prompts on existing files before you rely on it repeatedly. In practice, generate once, review the output, and commit it before hand-editing anything.
- Is yab/crudmaker safe to use in production?
- It is a scaffolding tool rather than a runtime dependency in the request path, which lowers the risk considerably. The bigger concern is that the repository is archived, so there are no security patches, framework compatibility updates, or upstream issue responses. Treat it as a disposable dev dependency and vendor the generated code into your application namespace.
- Does CrudMaker support API-only or headless Laravel applications?
- Poorly. It generates Blade views alongside controllers and routes, so roughly half its value disappears if you use a JS, Inertia, or Livewire front end. The migration and model generation may still be useful, but evaluate it as a narrower tool. For API-first builds, consider dedicated generators or writing your own stubs.
- Can I fork yab/crudmaker into a private repository?
- Yes, it is MIT licensed, and the archive status plus zero dependents suggest forking or internal ownership is the intended usage pattern. You can pin a fork in a private VCS and adapt it to your target Laravel version. Remember that once generated code lands in your repository it is your code forever, with no vendor to escalate to when something behaves subtly wrong.
- How many people use yab/crudmaker, and is it still maintained?
- It has roughly 31 stars and zero dependents, so there is effectively no community validation, no production corpus, and no Stack Overflow footprint to lean on. The repository is archived, which means no issue triage, no compatibility updates, and no security patches. The opportunity score of 4.91 suggests the capability is underserved, but that argues for building or forking the pattern internally rather than adopting this artifact as-is.
- What kind of Laravel architecture does CrudMaker fit?
- A conventional Laravel MVC monolith with server-rendered Blade views, a heavy admin or back-office surface, and a team that already accepts Eloquent as the domain model. It fits poorly with API-first builds, event-sourced or hexagonal architectures, or codebases where behaviour lives in domain services rather than controllers. Confirm the stack fit before anything else.
- Are the generated Blade views tied to a specific CSS framework?
- Likely Bootstrap-era markup, given the package was archived before modern Tailwind-based Laravel starters were standard. Either way, the generated views will need restyling to match your design system. Generate a sample entity early so you can estimate the cleanup cost before committing to the package.