Weave Code
Varieties Bundle Laravel Package
libre-informatique/varieties-bundle
A Symfony bundle for managing plant varieties, helping you model, organize, and expose variety data in agricultural or botanical applications. Integrates with Doctrine entities and provides a flexible foundation for variety catalogs and related taxonomy.
[DEPRECATED] Plant taxonomy management : Family / Genus / Species / Subspecies / Variety
Frequently asked questions about Varieties Bundle
- Can I install libre-informatique/varieties-bundle in a Laravel application?
- Technically Composer will install it, but nothing will happen at runtime. The package is a Symfony bundle, so it relies on bundle registration, a Symfony configuration tree, Doctrine ORM entity mappings, and Symfony form and routing conventions. Laravel has no service provider, config file, or auto-discovery hook for it, so composer require simply drops inert Symfony code into your vendor directory. Treat the entity design as a specification rather than a dependency.
- Is libre-informatique/varieties-bundle still maintained?
- No. The package is marked as deprecated by its own maintainers, has zero stars and zero dependents, and shows no upstream activity. There is effectively no one to consume security patches or bug fixes from. Since the repository is a bundle rather than a Laravel package, there is also no Laravel community around it to fall back on.
- What license does this varieties bundle use?
- The license reports as NOASSERTION, meaning there is no recognized SPDX identifier attached to the code. That is a procurement and legal blocker before any code is reused, regardless of technical merit. Before copying entity definitions or schema into your own project, confirm with the originating organization whether fork, modification, and redistribution are permitted.
- Does this package support Laravel 10 or Laravel 11?
- No. This is a Symfony bundle, so its version constraints target Symfony and Doctrine majors rather than Laravel releases. There is no Laravel service provider, facade, or config publication step to wire it into a Laravel 10 or 11 application. Its Symfony and PHP constraints are also likely pinned to an end-of-life major, which means a PHP upgrade would break it silently.
- How does the variety taxonomy model work in this bundle?
- It defines a ranked taxonomy chain of Family, Genus, Species, Subspecies, and Variety, with variety entities carrying botanical and commercial attributes. Related metadata is stored on Doctrine-backed entities, and a service layer handles querying and managing the records. That chain is a legitimate reference design for seed catalogs, nursery inventory, crop research, and agri-commerce, even if you never install the code.
- How do I reimplement this variety model in Laravel with Eloquent?
- Use the entity design as a specification and build the taxonomy chain natively in Eloquent. For the hierarchy, choose an adjacency list with a parent_id column for simple reads, or a closure table if you need fast ancestor and descendant queries at depth. Map the Family through Variety ranks to your own models, add descriptive metadata as JSON columns or a separate attributes table, and keep the variety record separate from static reference taxonomy.
- Does this bundle handle synonyms, authority cross-references, and cultivar naming?
- Based on the documented scope, it covers taxonomy structure only. Synonym handling, authority cross-references, and cultivar naming conventions are not described, so do not assume they are covered. If your product needs those, plan to model them yourself and validate against authoritative sources.
- Is it safe to depend on this package in a production Laravel app?
- No. Risk concentrates in the artifact: it is already deprecated, the license is unresolved, dependency constraints are likely pinned to an end-of-life Symfony major, and there is no upstream to consume security patches from. The mitigating factor is that plant taxonomy is a mature, well-documented domain, so business continuity survives losing the code. That asymmetry is what makes reference-not-dependency the correct posture.
- What should I use instead of this bundle for plant variety data in Laravel?
- There is no direct Laravel equivalent, so the practical path is to build the catalog natively in Eloquent and seed it from authoritative taxonomy sources. POWO, IPNI, GBIF, ITIS, EPPO, and GRIN-Global all publish well-structured reference data you can import and reconcile. Keep static reference taxonomy separate from customer-specific varietal records, because those are different modeling problems.
- Is this bundle part of a larger ecosystem that affects adoption?
- Yes. It is designed to interoperate with related Libre Informatique SIL bundles such as crop, seed-lot, and producer, so isolated adoption is not what it was built for. Pulling in one piece drags in assumptions about the others, along with bundle registration and Doctrine plumbing. Realistic integration is read, extract, or reimplement, not install and use.
Weaver
How can I help you explore Laravel packages today?