Weave Code
Orm Bundle Laravel Package
silpo-tech/orm-bundle
Silpo Tech ORM Bundle is a lightweight PHP ORM integration for bundle-based applications. It simplifies entity mapping, repository access, and database persistence, helping teams keep data handling clean, consistent, and easy to configure without a heavy framework footprint.
A Symfony bundle that contains common used ORM classes (e.g. Validators and Connection for retries)
Frequently asked questions about Orm Bundle
- Can I use silpo-tech/orm-bundle in a Laravel application?
- No, not as a drop-in dependency. silpo-tech/orm-bundle is a Symfony bundle, so it expects a Symfony kernel, a Bundle subclass, DI Extension and Configuration classes, and a compiler pass pipeline that Laravel does not provide. It also sits on Doctrine ORM, while Laravel is Eloquent-native. You could add laravel-doctrine as a shim or copy the specific classes you need, but both are architectural decisions rather than a simple Composer install.
- How do I install silpo-tech/orm-bundle?
- For a Symfony app you would require the package with Composer, enable the bundle in bundles.php, and configure it through your Symfony config. In Laravel there is no equivalent bundle registration step, so installation is only meaningful if you first add a Doctrine integration layer. Before committing, inspect composer.json for the PHP floor, Doctrine major version, and supported Symfony releases, because those constraints are not clearly documented.
- What does silpo-tech/orm-bundle actually contain?
- The description points to a thin utility layer of commonly used ORM classes, including validators and a connection wrapper for retries. It was extracted from Silpo's internal application, so expect repository helpers, query or filter builders, pagination, and entity traits with implicit conventions around naming and audit fields. Treat the inventory as unverified until you audit the source yourself.
- Does silpo-tech/orm-bundle work with Eloquent?
- No. The helpers are built around Doctrine concepts such as the entity manager, metadata, and Doctrine repositories, not Eloquent models and query builders. Making it work with Eloquent would mean rewriting essentially all of the useful behavior. At that point the bundle is a reference design rather than a dependency.
- Which Laravel, PHP, Symfony and Doctrine versions are supported by silpo-tech/orm-bundle?
- That information is not established in the public repository and needs verification. The repo shows zero stars and zero dependents, and the listed release date looks anomalous relative to the project's apparent maturity. Check composer.json for the PHP constraint, whether Doctrine is 2.x or 3.x, and which Symfony majors are actually supported before you trust the versioning scheme.
- Is silpo-tech/orm-bundle production-ready and actively maintained?
- Treat it as high risk for production use. There are no external consumers, no community CVE monitoring, no ecosystem pressure on version constraints, and the bus factor is the Silpo internal team whose priorities are not yours. There is also no evident public roadmap, changelog, or SemVer contract. Use it as a source of extractable PHP rather than a trusted long-term dependency.
- What are the alternatives to silpo-tech/orm-bundle for Laravel?
- For Laravel, start with Eloquent-native first-party helpers and only adopt Doctrine in Laravel if the team has already standardized on it. If you need connection retry behavior, implement it around Laravel's database layer or use a maintained community package. Pattern-mining this bundle for good ideas and writing your own helpers is the lowest-risk alternative.
- How would I migrate from silpo-tech/orm-bundle to Laravel?
- The recommended path is pattern-mining: read the helper implementations, adopt the useful ideas, and write first-party helpers that match your conventions. If a class is genuinely non-obvious, selectively vendor it under your namespace with MIT attribution and a provenance note. Using it as a Composer dependency plus Doctrine is only defensible when Doctrine is already your standard in Laravel. Rough effort is one to two days to audit the API surface and three to five days to extract, retarget, and test.
- Can I copy code from silpo-tech/orm-bundle into my Laravel project?
- Yes, the MIT license permits copying, provided you keep the copyright and license notice. Selective vendoring is reasonable for a genuinely non-obvious helper, such as a well-tested filter or sort parser, but not for thin wrappers you could write in a day. Add a provenance note so future maintainers know where the code came from and why it was copied.
- How should I test silpo-tech/orm-bundle or helpers extracted from it?
- After extraction, cover the copied or rewritten helpers with your own unit and integration tests, especially the retry connection behavior using failure injection. Audit the API surface first so you know exactly what you are adopting, and verify the Doctrine major, PHP floor, and Symfony constraints against your stack. Also list transitive dependencies you would inherit and decide whether they are acceptable.
Weaver
How can I help you explore Laravel packages today?