Data Mapper Laravel Package

Product Decisions This Supports

• Build vs. buy/borrow: Treat this as a reference implementation, not a supported dependency. The MIT license permits forking, but with 1 star, 0 dependents, and no release since 2016, the real cost is “build and maintain internally.” It should not win a build-vs-buy decision on its own.
• Architecture roadmap: Useful input when deciding whether to decouple domain objects from Eloquent’s Active Record approach. A Data Mapper layer can improve testability, isolate persistence concerns, and support multiple storage backends—but this package is unlikely to be the vehicle for a modern Laravel roadmap.
• Feature scoping: Fits exploratory spikes where explicit mapping between domain objects and persistence is the point. Poor fit for CRUD-first features where Eloquent is sufficient and time-to-market matters.
• Use cases: Legacy PHP systems already using a Data Mapper style; architecture proofs-of-concept; migration evaluation from Active Record to Data Mapper; teaching/reference code. Avoid for greenfield production, security-sensitive systems, or long-lived products.

When to Consider This Package

• Consider only if: you are maintaining a legacy PHP/Laravel app pinned to pre-2017 runtime constraints; you need a permissively licensed reference implementation; you are running a short-lived architecture spike; and you have engineering capacity to fork, patch, and own it.
• Look elsewhere if: you need PHP 8+/modern Laravel compatibility, active security maintenance, documentation, community support, or a production support path. Prefer Doctrine ORM, Cycle ORM, or a repository pattern over Eloquent. If procurement weighs ecosystem signals, 1 star and 0 dependents should be treated as unproven and high-risk.

How to Pitch It (Stakeholders)

• Executives: “This is an abandoned, low-adoption open-source component. The MIT license means we could fork it, but we would own all maintenance and security. Recommendation: do not make it a strategic dependency—use it only as a reference or not at all.”
• Engineering: “It demonstrates a Data Mapper approach but has not shipped since 2016 and has no ecosystem. If we need this pattern, evaluate Doctrine/Cycle or budget for an internal fork. It is useful for a spike, not a production bet.”