- How do I install cgdprojects/genealogy in a Laravel application?
- There is no Composer package install path — the repository is a full Laravel 10 application, not a distributable library. You fork or clone the repo, run composer install against the July 2023 lockfile, and configure it as your own application. Treat it as a codebase you adopt and own, not a dependency you require.
- Is cgdprojects/genealogy a Laravel package or a full application?
- Despite the package framing, the metadata describes a complete Laravel 10 backend for family tree and genealogy processing. There is no semver contract, no documented public API, and no composer require integration model. Plan to fork it, extract the domain layer, or use it purely as a reference specification.
- Which Laravel and PHP versions does cgdprojects/genealogy support?
- It targets Laravel 10.x on PHP 8.2, with PHP 8.3 generally safe and PHP 8.4 untested at this vintage. Laravel 10 security support ended February 2025, and PHP 8.2 security support ends December 2026, so budget an upgrade sprint to Laravel 11 or 12 before long-term use.
- Does cgdprojects/genealogy support GEDCOM import and export?
- Yes — GEDCOM import and export are part of the stated feature set alongside the person, family, event, and relationship schema. Because no test coverage is published, verify round-trip fidelity in a due-diligence spike. Pay particular attention to source, citation, media, and living-person handling during import.
- Is cgdprojects/genealogy still maintained?
- No. The repository is archived, so there are no bug fixes, security responses, dependency updates, or maintainer to consult. Upstream bus factor is effectively zero. Once you fork it, you own 100% of maintenance, including the Laravel and PHP upgrade path.
- Is cgdprojects/genealogy safe to run in production?
- Proceed with caution. The 2023-era lockfile likely pins stale transitive dependencies with known CVEs, so run composer audit and remediate before deploying. Genealogy data is inherently personal, and mishandling living persons creates regulatory and reputational risk — verify authorization, privacy controls, and multi-tenancy first.
- How do I query ancestors and descendants with cgdprojects/genealogy?
- The domain layer models people, families, events, and relationships as Eloquent models and exposes relationship traversal for ancestors and descendants. Confirm how relationships are stored — adjacency list versus closure table — and whether queries rely on recursive CTEs or vendor-specific SQL. Test against both MySQL and Postgres if database portability matters to you.
- How do I extract the genealogy domain layer from cgdprojects/genealogy?
- Fork and freeze the repo, run composer audit, then inventory which models, migrations, GEDCOM services, and relationship logic are domain code versus disposable Laravel scaffolding. Write characterization tests against observed behavior before moving anything. Re-home the domain layer behind your own service boundary on a supported Laravel version and discard what you do not need.
- What is the test coverage and CI status of cgdprojects/genealogy?
- No coverage numbers or CI status are published for the archived repo. Verify in a spike by cloning, installing, and running the suite against your target PHP and database versions. Regardless of results, plan to author characterization tests around GEDCOM round-trips and ancestor/descendant traversal before you depend on the code.
- What are the alternatives to cgdprojects/genealogy for Laravel family tree software?
- If genealogy is your actual product, extracting the domain layer from this repo is the pragmatic path; otherwise build fresh on a supported Laravel version. Non-Laravel options like webtrees or Gramps exist but do not share the Eloquent and Blade stack. If extraction from this repo is not clean, use it as a reference specification rather than a foundation.