- Is grossum/core-bundle a Laravel package?
- No. grossum/core-bundle is explicitly a Symfony bundle and has no Laravel service provider, facade, publishable config, or Laravel version constraint. You cannot composer require it into a Laravel application without writing your own framework shim.
- Can I install grossum/core-bundle in Laravel 10, 11, or 12?
- Not realistically. A 2016-era package will almost certainly pin PHP ~5.6 or ~7.0 and Symfony ~2.x or ~3.x, while Laravel 10, 11, and 12 require PHP 8.1 or newer. Composer dependency resolution is expected to fail on constraint intersection before any code is evaluated.
- What Laravel version does grossum/core-bundle support?
- None. There is no Laravel version constraint and no evidence of Laravel integration in the package. Its last release in December 2016 predates modern Laravel versions entirely.
- How do I install grossum/core-bundle with Composer?
- For a legacy Symfony project the command would be composer require grossum/core-bundle, but that is not a Laravel installation path. In Laravel the package is a foreign-framework artifact, so installation would mean authoring an adapter rather than using Composer normally. Also review the GPL-3.0 license before adding it to any codebase.
- Is grossum/core-bundle still maintained?
- No. The last release was 2016-12-13, roughly nine years ago, with no commits, tags, or security patches since. It has 0 stars, 0 dependents, and a health score of 0.13, so there is no CVE response path or maintainer to escalate to.
- What license does grossum/core-bundle use?
- It uses GPL-3.0, which is copyleft. For a SaaS backend with no distribution it may be survivable, but shipped, on-prem, or embedded products create material legal exposure that requires counsel sign-off. Most commercial Laravel shops default to MIT or Apache-2.0 for this reason.
- What does grossum/core-bundle actually do?
- It packages shared core functionality for Grossum PHP applications, including reusable base components, common services, and centralised defaults. The public description does not prove whether the code is framework-agnostic core wrapped by Symfony or Symfony-entangled throughout. That distinction determines whether Laravel teams can extract anything useful or must rewrite it.
- How can I use grossum/core-bundle functionality in Laravel?
- The default recommendation is to reimplement from scratch, using the source as a specification and writing native Laravel code against current PHP. If an audit shows clean separation, you could vendor the framework-agnostic domain classes and add a fresh Laravel service provider, config file, and facade. Forking and porting wholesale is only justified if the codebase is large, dense with non-obvious business logic, and irreplaceable.
- Are there alternatives to grossum/core-bundle for Laravel?
- Yes. For commodity functionality, choose maintained MIT or Apache-2.0 packages with active Laravel support, or build the small amount of native Laravel code you need. An abandoned Symfony bundle is not a sensible alternative when modern Laravel components cover the same ground.
- Should I use grossum/core-bundle in production?
- No. It is abandoned, GPL-licensed, and has zero production validation we can point to, so it is a high-risk dependency. If you need the behavior, reimplement it or vendor only after a legal and LOC audit.