Weave Code
Data Bundle Laravel Package
imatic/data-bundle
A PHP data bundle from iMatic that packages shared data utilities for reuse across projects. It aims to cut boilerplate and keep data handling consistent, with a lightweight structure that fits into existing PHP applications.
Bundle to work with data
Frequently asked questions about Data Bundle
- Does imatic/data-bundle work with Laravel?
- No. It is a Symfony bundle that registers through the Symfony kernel and depends on Symfony's bundle and dependency-injection contracts, not Laravel's service container. There is no Laravel service provider, facade, or package discovery, so it will not boot under Laravel. Treat it as a reference for patterns rather than an installable dependency.
- Can I install imatic/data-bundle in a Laravel project with Composer?
- A direct Composer install is technically possible, but the bundle will not register or boot in Laravel. At best it adds dead weight and version pressure on Symfony components that Laravel already pins transitively. The feasible paths are cherry-picking specific helper classes into an internal package or reimplementing the ideas against Eloquent or DBAL.
- Which Laravel versions does imatic/data-bundle support?
- None officially. The package targets Symfony's bundle and dependency-injection system and has no published Laravel support matrix, service provider, or config contract. If you need a Laravel-native data layer, choose a package built for Laravel's container and Eloquent instead.
- Is imatic/data-bundle actively maintained?
- There is no strong evidence of active maintenance. The evaluation cites 1 star, 0 dependents, an aggregate score of 0.105, and no observable production usage to validate the API surface. Check the repository's last commit and release cadence before relying on it, and expect maintenance to follow the vendor's own project needs rather than yours.
- What does imatic/data-bundle actually do?
- The description is simply a bundle to work with data, and the evaluation notes that data bundles of this vintage typically wrap Doctrine or DBAL with query-building and hydration helpers. There is no clearly named capability that Eloquent, the query builder, or Doctrine DBAL does not already provide. Identify a concrete capability gap before considering any reuse.
- Does imatic/data-bundle require Doctrine?
- The evaluation says the data layer likely assumes Doctrine ORM metadata or at least DBAL, which determines whether porting is a day or a quarter. Retrofitting those abstractions onto Eloquent usually means a dual persistence layer or a rewrite. Confirm the Doctrine versus DBAL boundary by reading the source before scoping any extraction.
- What are Laravel-native alternatives to imatic/data-bundle?
- Use Laravel's native query builder and Eloquent, or a package such as spatie/laravel-query-builder for filtered and sortable queries. For lower-level access, Doctrine DBAL is an option. The evaluation's opportunity score of 19.06 suggests the value on offer is better obtained elsewhere.
- Is imatic/data-bundle safe for production?
- There is no security policy, no advisory history, and near-zero community scrutiny, which is a concern for a component that touches data access. With 1 star and 0 dependents, there is no external review to catch issues. Do not adopt it as a production dependency without a thorough internal audit.
- How do I test imatic/data-bundle in a Laravel application?
- You cannot test it as a Laravel package out of the box because it has no Laravel service provider or test harness for Laravel's container. Any meaningful testing would follow a manual port: extract the classes you need into an internal package and write your own tests against Eloquent or DBAL. Budget that work as a port, not an install.
- Can I vendor or fork imatic/data-bundle into an internal package?
- Yes, if the license permits it. The evaluation notes that a permissive license such as MIT is acceptable, but attribution and fork ownership must be documented; verify the actual license file in the repository before vendoring. Cherry-picking a small, framework-agnostic subset is the recommended path, and you should accept that you own the fork immediately. The exit cost depends on how many call sites you create.
Weaver
How can I help you explore Laravel packages today?