- Is mahefa/comment-bundle a Laravel package?
- No. It is a fork of FOSCommentBundle, which is a Symfony bundle, so it registers through a Symfony kernel and DI extension class rather than a Laravel service provider. The domain concepts, such as threaded comments, moderation state, and voting, are portable, but none of the integration seams are written for Laravel.
- Can I install mahefa/comment-bundle in a Laravel app with Composer?
- Practically no. The bundle carries Symfony 2.x and 3.x-era constraints that collide with the Symfony 6 and 7 components Laravel 10 and 11 already depend on, including http-foundation, console, and process. Composer will typically fail to resolve the dependency graph before you write a single line of integration code.
- Which Laravel and PHP versions does mahefa/comment-bundle support?
- None officially. The package targets the Symfony 2.x to 3.x era with Doctrine ORM, and there is no published CI matrix proving support for modern PHP. Treat it as unsupported on PHP 8.1+, Laravel 10, and Laravel 11 instead of assuming compatibility.
- What functionality does mahefa/comment-bundle actually provide?
- It supplies the core building blocks for threaded discussions: comment and thread entities, parent and child adjacency, moderation states, voting, and ACL-based permissions. The data model is a useful reference, but the implementation is tied to Symfony forms, Twig, Doctrine, and FOSRestBundle with JMSSerializer.
- How is mahefa/comment-bundle configured in an application?
- Through Symfony's DI extension, YAML or XML service definitions, and bundle registration in the kernel, not through Laravel config files. There is no config file to publish and no service provider to hook into. Any settings you want in Laravel, such as moderation states, spam hooks, or rate limits, have to be rebuilt from scratch.
- How would I port mahefa/comment-bundle to Laravel?
- Map the Doctrine entity graph to Eloquent models and migrations, and replace annotations with PHP 8 attributes. Extract threading and moderation into framework-agnostic services bound in a service provider, then expose them through FormRequests, API Resources, and policies. Replace the adjacency-list recursion with materialized path or nested-set columns so subtree reads stay a single indexed query. Budget a spike of a few days, because this is a rewrite rather than an integration.
- Is mahefa/comment-bundle actively maintained?
- There is a single release dated 2022-08-10, zero stars, and no known dependents, while upstream FOSCommentBundle was effectively abandoned years earlier. That combination means no downstream canary, no CVE watch, and a bus factor of one. If you adopt any of it, plan on owning the maintenance yourself.
- What is a good Laravel alternative to mahefa/comment-bundle?
- For most teams the realistic options are a scoped in-house build or a currently maintained Laravel commenting package that ships migrations, policies, and Blade or Inertia components. Because this bundle cannot be installed in Laravel, compare alternatives on active releases, test coverage, and a security disclosure channel rather than on feature checklists.
- Is mahefa/comment-bundle safe to run in production?
- There is no published security contact, no CVE history, and no CI signal, so adopting it means accepting unknown risk. The Symfony-era transitive dependencies it expects, such as FOSRestBundle, JMSSerializerBundle, and SensioFrameworkExtraBundle, are themselves retired or in maintenance. For a production Laravel app, keep it out of your runtime dependencies and treat it as a design reference only.
- Does mahefa/comment-bundle include tests or CI I can rely on?
- There is no meaningful public signal on test coverage or continuous integration for the fork, and one 2022 release gives no evidence of a supported version matrix. If you port the schema or threading logic, write your own feature tests for reply nesting, moderation transitions, and per-thread authorization. Do not assume the upstream test suite still reflects the fork's code.