- What is yab/laracogs used for?
- yab/laracogs is an opinionated scaffolding toolkit for Laravel 5.x that generates common application features such as CRUD screens, roles, teams, invitations, notifications, billing, two-factor auth, and an admin dashboard. Most of its value is written into your application as generated code and boilerplate rather than consumed as a runtime library. It also ships artisan generators and service classes and facades for recurring product primitives. It was last released in 2017 and is archived.
- Is yab/laracogs compatible with Laravel 10 or Laravel 11?
- No. The package's Composer constraints are pinned to Laravel 5.x and contemporaneous dependencies, so it will not resolve against Laravel 9, 10, 11, or 12 without a fork and dependency surgery. Its conventions are also tied to Laravel 5.4/5.5-era service providers, facades, and view scaffolding. The only realistic fit is a legacy Laravel 5.x application already frozen on that framework line.
- How do I install yab/laracogs?
- Installation is via Composer as yab/laracogs, but it will only resolve in a Laravel 5.x project with compatible PHP and transitive dependency versions. On modern Laravel or PHP 8.x stacks, Composer resolution is expected to fail before installation completes. In a legacy project you would wire up the package's service provider and then run its generators. Because the package is archived, treat any install as a one-time scaffold generation rather than a maintained dependency.
- Does yab/laracogs work with PHP 8?
- It is not designed for PHP 8. Code from its 2017-era release commonly hits PHP 8.x issues such as dynamic property deprecations, removed each(), curly-brace string offsets, and implicit nullable parameter deprecations. Even if it loads after patching, behavior may differ from the original PHP 7.0/7.1 target. The supported stack is effectively Laravel 5.4/5.5 with PHP 7.0/7.1.
- Is yab/laracogs still maintained?
- No. The repository is archived and the last release was 2017-08-31, with zero dependents indicating little ongoing ecosystem use. The roughly 977 stars and 4.75 score reflect 2015-2017 momentum rather than current viability. There is no upstream path for fixes or security remediation.
- Which Laravel and PHP versions does Laracogs support?
- The realistic target is Laravel 5.4/5.5 with PHP 7.0/7.1. Its Composer constraints are pinned to Laravel 5.x and contemporaneous transitive packages, including Backpack. It is not supported on Laravel 8+ or PHP 8.x without a fork and patching. Treat any other version combination as unsupported.
- What features and generators does Laracogs provide?
- It provides artisan generators such as laracogs:crud, laracogs:bootstrap, laracogs:facades, and laracogs:make, plus services and facades for billing, blog, FAQ, notifications, roles and permissions, settings, teams, two-factor auth, and theming. The CRUD generator historically sits on top of Backpack for Laravel's admin panel. It also includes an admin dashboard and boilerplate for users, roles, teams, and invitations. Most features are generated into your app rather than provided as a versioned runtime dependency.
- Can I use Laracogs as reference code instead of a dependency?
- Yes, that is the safer use. Because most of Laracogs' value is generated into the host app, you can harvest patterns for roles, teams, settings, 2FA, billing, and admin screens without carrying it as a dependency. But review and modernize anything security-sensitive, since the code is 2017-era and has no upstream fixes. Do not copy generated auth or billing code without a security review.
- Is Laracogs safe to use in production?
- Generated authentication, two-factor, billing, and authorization code has no CVE feed or upstream patching path because the package is archived. You own triage and remediation for any security-sensitive output from day one. The abandoned transitive dependencies add further risk, and generated scaffolds can drift across teams without a shared versioned template source. It is not recommended for production adoption as a dependency.
- What are good alternatives to Laracogs for Laravel scaffolding?
- For modern Laravel, evaluate maintained tools for each primitive instead of one archived toolkit: Laravel Breeze or Jetstream for auth scaffolding, Laravel Fortify for authentication backends, Laravel Cashier for billing, Spatie packages for roles and permissions, and Backpack or another maintained admin panel for CRUD. These are versioned dependencies with active security and upgrade paths. The right alternative depends on which specific primitives you were trying to accelerate.