- Is free-agent/workflow-bundle compatible with Laravel?
- No. free-agent/workflow-bundle is a Symfony2 bundle built to be registered in a Symfony Kernel, configured through Symfony's Configuration/Extension tree, and wired into the Symfony DI container and EventDispatcher. Laravel has no bundle concept, so there is no drop-in path. You would have to extract the core state-machine classes and re-host them inside a Laravel service provider, assuming they are decoupled enough to allow it, which is unlikely.
- Can I just run composer require free-agent/workflow-bundle in a Laravel 10 or 11 app?
- Composer may resolve the install, but a successful require does not mean the code will load. The bundle's service definitions assume Symfony 2.x component versions, which conflict with the Symfony 6/7 components Laravel pulls in transitively. Expect either dependency-resolution failures or, worse, an install that succeeds and then throws container errors at runtime.
- What should I use instead of FreeAgentWorkflowBundle in a Laravel application?
- Replace rather than port. The primary recommendation is the symfony/workflow component used standalone: it is the maintained successor to the ideas in this bundle, framework-agnostic by design, supports modern PHP, and can be bound into Laravel with a thin service provider that registers the Workflow and MarkingStore factories. If your requirement is per-model state with typed transitions and authorization hooks, spatie/laravel-model-states is the more Eloquent-native alternative.
- How do I register a Symfony2 bundle in a Laravel service provider?
- There is no supported way to do this. A bundle's service definitions, extension configuration and event wiring all assume Symfony's container and dispatcher, while Laravel uses service providers, the Illuminate container and its own event system. Any adapter would first have to prove the workflow engine is separable from the Symfony2 wiring, which is an estimated 2 to 4 engineering days of spike work with a likely negative answer.
- Does free-agent/workflow-bundle support PHP 8 and modern Symfony components?
- PHP 8.x compatibility is unverified and unlikely. The package targets the Symfony 2 era, meaning PHP 5.x and early 7.x, and it has no PHP version support statement beyond that. With no maintainer and no upstream fixes, nothing will change that.
- Is free-agent/workflow-bundle still maintained?
- No. The repository is archived with no maintainer, so there are no upstream fixes and no security patches. Health signals are uniformly negative: roughly 2 stars, 0 dependents and a score of 0.035, with no evidence of production use anywhere. Adopting it means owning a fork forever, because there is no community to consult when something breaks.
- What is the difference between a Symfony bundle and a Laravel package?
- A Symfony bundle plugs into the Symfony Kernel, its Configuration/Extension tree and the Symfony DI container, and it is discovered through the bundle registration mechanism. A Laravel package ships service providers that register bindings in the Illuminate container and hook into Laravel's own event dispatcher and lifecycle. The two integration models are not interchangeable, which is why a Symfony2 bundle is not a natural citizen of a Laravel application.
- How do I build multi-step approval or order lifecycle workflows in Laravel?
- Start from the workflow semantics you actually need: simple state transitions, guards, transitions with side effects, or full Petri-net-style places and transitions with marking. For general orchestration, bind the standalone symfony/workflow component into Laravel through a thin service provider. For per-model state such as an order lifecycle or approval chain, spatie/laravel-model-states is usually the closer fit.
- Is it safe to use an abandoned Composer package in production?
- Abandonment is the dominant risk here rather than supply-chain compromise; the MIT license and tiny footprint keep the attack surface small, but you get no patches and no one to ask for help. The dangerous outcome is silent failure: a package that installs and then behaves subtly differently from its original Symfony2 assumptions under Laravel's container and event lifecycle. If you adopt it, budget for permanent fork ownership and an accepted cost of that ownership over 24 months.
- How do I test workflow state transitions in a Laravel app?
- free-agent/workflow-bundle ships nothing for Laravel testing, and its Symfony2 wiring makes container-level tests awkward to reproduce under Illuminate. If you move to symfony/workflow standalone, the workflow definition and marking store can be constructed directly in a unit test, so you can assert allowed and blocked transitions without booting the full framework. Pair that with feature tests on the Eloquent model if you use spatie/laravel-model-states.