- What is fanamurov/larrock-core and what does it do?
- It is the core package for LarrockCMS built on Laravel, providing the admin panel foundation, module registration, CRUD scaffolding, and shared services used by Larrock content modules. It is not a standalone feature library; its value is realized alongside the sibling Larrock admin and content packages. Adopting it means adopting LarrockCMS's architectural opinions wholesale.
- Which Laravel and PHP versions does larrock-core support?
- The decisive check is the illuminate/* constraint in composer.json against your target Laravel version. A package with this age and adoption profile is plausibly pinned to an older Laravel major, which turns integration into an upgrade or fork. Confirm supported PHP versions at the same time before starting any spike.
- How do I install larrock-core in a Laravel application?
- Installation is mechanically straightforward: Composer require, service provider auto-discovery, vendor:publish for config, migrations, and assets, then run migrations. The real effort is reconciliation, not installation. Ensure table prefixes, auth guards, middleware stack, and admin routing do not collide with the host application.
- How should I configure larrock-core alongside an existing admin panel?
- Decide your admin strategy first. If the product already uses Filament, Nova, or a custom admin, adopting LarrockCMS creates two admin planes, so pick one rather than running both. Also check whether the package registers global helpers, view namespaces, facades, or Blade directives, since that surface becomes a persistent conflict and debugging source.
- Is larrock-core a good alternative to Filament or Nova?
- It is a competing admin paradigm, not a complement to Filament, Nova, or Inertia-based admin stacks. For a team already standardized on Laravel, the Eloquent-centric models and Blade-rendered admin screens are familiar. It fits best when a batteries-included Laravel CMS is cheaper than assembling one, such as an internal back office or content-driven site.
- What license does larrock-core use, and can I use it commercially?
- GitHub reports NOASSERTION for this package, meaning it could not detect a recognized license. Redistribution and derivative-work rights are undefined until counsel reads the actual LICENSE file and composer.json metadata. This alone can block adoption in a commercial or redistributed product, so gate everything behind that review.
- Can I use larrock-core with a custom user model, UUID keys, or multi-tenancy?
- CMS cores commonly assume a fixed user model, auth guard, table prefix, and route namespace, and those are the usual breakpoints for custom setups. UUID or ULID primary keys, non-standard user models, custom guards, and multi-tenancy should each be verified explicitly rather than assumed to work. Test these against a clean Laravel skeleton at the pinned version before committing.
- Does larrock-core have tests and CI coverage?
- Test coverage is unknown from the available information, so verify CI status and the presence of tests before adopting. Pay particular attention to coverage on the boot, config, and migration paths. Without tests, every Laravel minor upgrade becomes a manual regression exercise.
- Is larrock-core actively maintained and safe for production?
- With 44 stars and a single-maintainer profile, community redundancy and bus factor are low. Do not assume a security disclosure process, a release cadence, or an LTS commitment. For production, pin the version, run your own audit, and plan for Russian-language documentation that may require translation and reverse-engineering.
- Is there a documented upgrade path for larrock-core between Laravel majors?
- There is no stated upgrade policy in the available context, so treat each Laravel major bump as a possible fork rather than a routine update. Ask the maintainer whether a documented upgrade path exists and who is accountable for security issues. If none exists, budget for maintaining a fork or staying pinned.