Weave Code
Flexmodel Bundle Laravel Package
flexmodel/flexmodel-bundle
FlexModel Bundle offers a flexible model layer for Laravel/PHP applications, enabling dynamic attributes, relationships, and configurable schemas with less migration overhead. A practical fit for rapid prototyping and customizable data structures.
FlexModel integration for Symfony 3+.
Frequently asked questions about Flexmodel Bundle
- Is flexmodel/flexmodel-bundle compatible with Laravel?
- No. FlexModel Bundle is a Symfony bundle built around a Bundle class, a DI extension, compiler passes, and YAML service definitions, none of which Laravel's container uses. Laravel resolves services through service providers and config arrays, so the bundle layer provides no usable integration. Only the underlying flexmodel/flexmodel core library could theoretically be wired by hand.
- Can I install FlexModel Bundle in Laravel 10 or 11?
- It will almost certainly fail Composer resolution. The bundle targets Symfony 3-era components, while Laravel 10 and 11 sit on Symfony 6 and 7, so requiring symfony/framework-bundle ^3.x conflicts with the framework's own dependency tree. That is a fast, visible failure at install time rather than a silent runtime problem.
- Does FlexModel Bundle support PHP 8.2?
- There is no declared support for modern PHP. The package dates from the PHP 7.0 and 7.1 era and was archived in January 2018, well before PHP 8's dynamic-property deprecations and tightened return types. That vintage of code often produces fatal errors rather than warnings on PHP 8.2 and above.
- What is the difference between flexmodel/flexmodel-bundle and flexmodel/flexmodel?
- The bundle is Symfony packaging: it registers the core library's services, exposes configuration for model paths, and supports autowiring and kernel conventions. The core library is the actual model layer with dynamic attributes and configurable schemas. For a Laravel team, only the core library is even theoretically reusable, and it would have to be wired manually.
- What are Laravel alternatives to FlexModel Bundle for dynamic attributes?
- The native approach is JSON or JSONB columns on existing tables with custom Eloquent casts and validation rules. If you need a dedicated store, spatie/laravel-schemaless-attributes or a controlled attribute/value table with a domain-owned schema registry are practical options. All of these keep you on supported first-party primitives and preserve Eloquent query ergonomics.
- Is flexmodel/flexmodel-bundle still maintained?
- No. The repository is archived, the last release was January 2018, and it has one GitHub star and zero dependents. There is no issue triage, security feed, or compatibility maintenance. Any fork you create becomes your own CVE responsibility.
- How do I install flexmodel/flexmodel-bundle?
- In a Symfony application you would require the package with Composer, register the bundle in your kernel, and configure model paths through the bundle's config tree. In Laravel there is no equivalent registration step, and Composer resolution is expected to fail because of Symfony component version conflicts. The documented install path assumes Symfony full-stack, not Laravel.
- Can I use FlexModel Bundle with Eloquent models?
- Not directly. The bundle provides Symfony service wiring for the FlexModel library, not an Eloquent integration, so there are no model traits, casts, or query builder hooks for Laravel. You would be building that bridge yourself, and the underlying schema-on-the-fly approach does not map cleanly onto Eloquent's query ergonomics for filtering and aggregation.
- Is FlexModel Bundle safe for production Laravel applications?
- The risk is high. An archived 2018 dependency with no security feed will not pass a serious composer audit or SBOM review, and the flexible attribute model is EAV-adjacent, which brings query performance, referential integrity, and reporting problems a thin unmaintained library does little to solve. If you need filtering or aggregation on flexible attributes, this pattern is likely a non-starter regardless of package quality.
- How should I evaluate FlexModel Bundle for a Laravel project?
- First clarify the actual requirement: user-defined custom fields on existing entities, or a genuinely open-ended model layer. Then compare native options such as JSON columns with Eloquent casts, spatie/laravel-schemaless-attributes, or a first-class attribute table you control. If you still want the core library, treat the bundle as non-installable and run a time-boxed spike on flexmodel/flexmodel directly, with a named owner and an agreed exit cost.
Weaver
How can I help you explore Laravel packages today?