Laravel Gedcom Laravel Package

Product Decisions This Supports

• Genealogy / family-history feature feasibility: This package wraps GEDCOM (the standard genealogical data interchange format) in Laravel idioms, so it directly informs whether you can support import/export of family trees, ancestor/descendant traversal, and interoperability with tools like Ancestry, MyHeritage, Gramps, or FamilySearch without building a parser from scratch.
• Build vs. buy: v8.6.0 signals an actively maintained package — a contributor-driven fix resolving Source through Laravel's service container (PR #94) and CI work to support Laravel 13 (PR #93). That reduces the "abandoned dependency" risk that usually tips a build-vs-buy decision toward building in-house.
• Platform upgrade sequencing: The Laravel 13 CI fix is a leading indicator that the package intends to track the framework's release cadence. This feeds directly into your upgrade roadmap — you can reasonably plan a Laravel 13 migration without treating this dependency as a blocker.
• Extensibility / customization decisions: PR #94 moving Source resolution to the container means the generator is now more DI-friendly. That supports a decision to extend rather than fork — you can bind your own Source implementation (e.g., a repository-backed source, an audit-logging decorator) without patching vendor code.
• Data-portability commitments: GEDCOM import/export is a common "no lock-in" promise in genealogy products. This package underpins the product decision to let users export their full tree in a standard format.
• Use cases: family-tree CRUD apps, genealogy SaaS, archival/heritage projects, migration tooling from legacy desktop genealogy software, and research-collaboration platforms that need to exchange records with third parties.

When to Consider This Package

Adopt when:

• Your domain genuinely involves GEDCOM — family trees, lineage records, archival genealogy. This is a narrow, standards-specific package; it is not a general-purpose data importer.
• You want Laravel-native integration (service container bindings, facades, config-driven behavior) rather than a standalone PHP parser you would have to wrap yourself.
• You need both read and write — GedcomGenerator producing output is a meaningful part of the value; pure-parsing alternatives may be simpler if you only ingest.
• You are on, or planning to move to, Laravel 13 — v8.6.0's CI changes suggest first-class support intent, though verify the framework constraint in composer.json before committing.
• You value maintainer responsiveness: two first-time contributors landing fixes in a single minor release is a healthy community signal for a niche package.

Look elsewhere when:

• Your data model is not genealogical. Forcing GEDCOM semantics onto unrelated records adds coupling with no payoff.
• You need round-trip fidelity guarantees on arbitrary third-party GEDCOM files. Validate against real-world exports from Ancestry/Gramps first; GEDCOM dialects vary widely and a minor release will not change that.
• You require a strictly versioned, vendor-backed SLA. This is community-maintained; the v8.6.0 changes are maintenance-level and the release history should be reviewed for breaking-change frequency before you depend on it in a regulated context.
• Your only need is a one-off import — a script or a lighter parser may be the better call than a persistent dependency.
• PR #94 is directly relevant to you: if you have subclasses or overrides around GedcomGenerator that assumed direct Source instantiation, confirm the container-resolved path does not alter your binding expectations.

How to Pitch It (Stakeholders)

For executives: This release confirms the genealogy integration library we'd use for family-tree import/export is alive and tracking modern Laravel. Two community contributors shipped fixes — one enabling the current framework generation, one making the export component more cleanly pluggable. Translation: lower integration risk and a credible "export your data in the industry-standard format" story for customers, at low cost versus building a GEDCOM engine ourselves. The caveat to state plainly is that it's community-maintained and genealogically specialized — it is a good bet for a genealogy feature, not a general data platform.

For engineering: v8.6.0 is a low-risk minor bump — no breaking changes or deprecations announced. It delivers Laravel 13 readiness in CI and resolves Source through the service container inside GedcomGenerator, which is a meaningful ergonomics and testability improvement: you can now bind custom Source implementations instead of relying on implicit construction. Recommended actions: verify the illuminate/* constraint in composer.json before upgrading, add a fixture-based round-trip test using a real third-party GEDCOM export, and audit any local overrides of GedcomGenerator for assumptions about how Source is instantiated. If those pass, this is a safe patch-level upgrade with a small architectural upside.