- Is feral/core a Laravel package?
- feral/core is the foundational core for the Feral PHP framework, not a conventional Laravel package. The 1.0.0 release explicitly positions it as a library available for any framework, and no Laravel service provider or adapter is included. You would need to write and maintain any Laravel integration glue yourself.
- How do I install feral/core with Composer?
- The Composer package name is feral/core, so installation is done through Composer rather than a Laravel package installer. The assessment recommends verifying resolution with composer why-not and composer install instead of trusting the 1.0.0 tag. Confirm the remaining require and require-dev entries at the tag, since symfony/* and Docker were removed.
- Does feral/core support Laravel 10 or Laravel 11?
- The release notes do not state Laravel version support, and the provided context contains no illuminate/* constraint evidence. Symfony removal improves PHP and package constraint compatibility, but the assessment still flags PHP/Laravel drift as medium risk. Test Composer resolution against your target Laravel and PHP 8.3 or 8.4 versions.
- What changed with Symfony dependencies in feral/core 1.0.0?
- The 1.0.0 release removed symfony/* from the dependency graph, which materially reduces the classic Composer conflict risk in an existing Laravel application. The release does not state whether HTTP foundation, routing, console, or DI primitives were reimplemented internally or delegated to the host framework. Audit the diff to determine which approach was taken.
- Is feral/core safe for production use?
- There is no evidence of production use, no CVE feed or advisory path, and no maintainer bench beyond the original author. The assessment rates abandonment and security posture as high risk. Treat 1.0.0 as a stability claim rather than proof, and audit the subtractive refactor before production adoption.
- How is feral/core tested?
- The provided assessment says nothing in the release notes indicates new tests, CI, documentation, or example integrations at 1.0.0. That absence is a code-quality and documentation risk, especially because the release is a large subtractive refactor. Audit the diff and look for test coverage in the repository rather than relying on the version number.
- Can I use feral/core without adopting the full Feral framework?
- The package is designed as a lightweight base for the Feral ecosystem, and 1.0.0 claims to be a true library available for any framework. However, no framework adapters are provided, so integration with Laravel or another host is bespoke. You would own the adapter burden entirely.
- What license does feral/core use and what is the open-core model?
- The core is Apache-2.0 licensed, but the assessment notes that open core typically leaves the editor, runtime, or connectors behind a commercial license. The 1.0.0 release does not clarify that boundary. Confirm the commercial roadmap and licensing split before committing.
- What are alternatives to feral/core for modular Laravel applications?
- If you need conventional Laravel modularity, standard Laravel packages, service providers, and Composer libraries are lower-risk because they follow explicit Illuminate contracts. feral/core is metadata-driven and low-code oriented, which creates a paradigm collision with hand-written Laravel controllers, models, and policies. Decide whether you need a framework core or a Laravel-native package.
- Is feral/core actively maintained?
- The 1.0.0 release follows roughly a three-year gap and is a single packaging change, which the assessment treats as a signal of life rather than sustainable maintenance. The bus factor remains unchanged with the original author. Check recent commit activity and issue response before depending on it.