- Can I use th3mouk/cms-core-bundle in a Laravel application?
- No. Despite often being filed under Laravel/PHP packages, this is a Symfony bundle: it ships no Laravel service provider, no publishable PHP config file, and no package auto-discovery, so Composer may install it but Laravel will never boot it. There is no adapter or bridge in the repository. Reject it on stack grounds for any Laravel roadmap item and spend zero engineering hours on it.
- What does th3mouk/cms-core-bundle actually provide?
- It is a scaffolding meta-package whose stated purpose is supplying dependencies and default configuration for the author's CMS Starter project, so its value is dependency pinning and opinionated defaults rather than domain logic. It is described as early-stage with limited adoption and sparse documentation. If you want to know whether there is any real code inside, check whether the bundle contains a DI extension, compiler passes, entities, or controllers, or only composer.json plus YAML. That single answer changes reuse effort by an order of magnitude.
- Which Symfony and PHP versions does th3mouk/cms-core-bundle support?
- Its constraints were frozen at the point the repository was archived, so expect version pins tied to whichever Symfony release the author was using at the time. On a current Symfony 6.4 or 7.x LTS with PHP 8.2 or newer, plan for Composer constraint conflicts, deprecation noise, and possible fatal errors from framework APIs that have since been removed. Read composer.json before attempting an install and treat any conflict as a hard stop rather than something to patch around.
- Is th3mouk/cms-core-bundle still maintained?
- No. The project is archived with no active maintainer, no issue triage, and no security response path, and it has zero dependents, which means there is no evidence anyone has run it outside the author's own starter project. Abandonment is a permanent risk you cannot mitigate from the outside unless you fork and take ownership. Treat it as frozen code, not as a dependency with an upstream to track.
- How do I install th3mouk/cms-core-bundle with Composer?
- You would run composer require th3mouk/cms-core-bundle inside a Symfony application, since there is no Laravel installation path. Resolution will most likely succeed only against the Symfony version the bundle was authored for, and will fail or produce warnings on newer LTS releases. If the companion CMS Starter project is also archived, there is no upstream to inherit an upgrade path from, so any install you get working is one you maintain yourself.
- What transitive dependencies does th3mouk/cms-core-bundle pull in?
- As a meta-package it drags in a dependency graph you did not select and cannot patch upstream, which is the core supply-chain concern here. Enumerate the full transitive tree and flag how many of those packages are themselves abandoned or unpatched. Any CVE in a pinned dependency becomes your incident, your disclosure, and your disclosure timeline, so that count belongs in the risk register before adoption is even discussed.
- Does th3mouk/cms-core-bundle have a test suite or CI history?
- Documentation is sparse and the repository shows limited activity, so do not assume a meaningful behavioural contract exists. Check for a test suite and CI history rather than a single squashed commit; with no tests, any fork you create inherits undefined behaviour you will have to reverse-engineer. Publicly available information is thin enough that you should verify this directly in the repository before scheduling any work.
- Is th3mouk/cms-core-bundle safe to use in production?
- Treat it as high risk. The package is unmaintained, exposes you to transitive dependencies you cannot patch, and sits in a CMS-adjacent area where routing, admin UI, and authentication inherit a much higher security bar than a utility library. An unmaintained bundle cannot meet that bar, and no maintainer means no coordinated disclosure path. The MIT license is the one clean element: forking is legally unencumbered, which matters for reference use and not at all for the dependency path.
- What are the alternatives to th3mouk/cms-core-bundle?
- On Laravel, evaluate maintained, framework-native options such as Filament for admin panels, Statamic or October CMS for content-managed sites, or a headless CMS behind an API. On Symfony, look at Sulu, Contao, or Symfony CMF rather than a frozen starter bundle. In many cases roughly fifty lines of configuration in your own application skeleton expresses everything this bundle enables, which removes the supply-chain question entirely.
- Can I fork th3mouk/cms-core-bundle or use it as a reference for my own skeleton?
- Yes, the MIT license makes forking legally straightforward, and reading it as a reference is the more sensible path than depending on it. Scope the effort first: if it is only composer.json plus YAML defaults it is a half-day read, whereas an executable bundle with a DI extension, compiler passes, entities, and controllers is closer to a two-week extraction. Either way, ask which specific starter features it enables that you could not reproduce as a small amount of configuration in your own skeleton; if the answer is none, it has no reason to exist in your stack.