Common Laravel Package

Product Decisions This Supports

• Adoption decision: Do not adopt orkestra/common for a new Laravel/PHP product. It is a Doctrine 2 utility package, not Laravel-native, with only 1 GitHub star, 0 dependents, and a last release in 2014.
• Build vs. buy: Treat this as a build internally or use maintained alternatives decision. Any “common functionality” it provides is likely small enough to implement directly, and the maintenance/security risk of an abandoned dependency outweighs reuse value.
• Roadmap and feature planning: This package should not influence roadmap commitments. It does not provide a strategic capability for modern Laravel applications and should not be planned into new features.
• Legacy support scoping: It may be relevant only when assessing an existing Doctrine 2 legacy system. Use it as a signal to budget for modernization, vendor-and-patch work, or replacement rather than extending dependence.
• Dependency governance: Use this package as a case study for enforcing minimum maintenance standards: recent releases, compatible PHP versions, community adoption, dependents, and security posture.

When to Consider This Package

Consider it only when all of the following are true:

• The product is an existing legacy PHP application already using Doctrine 2, not a Laravel/Eloquent application.
• The runtime PHP version is compatible with a package last released in 2014.
• The needed functionality is small, isolated, and can be vendored, forked, or replaced with low effort.
• Engineering has explicitly accepted the maintenance, security, and upgrade risk.
• There is a concrete cost saving versus rebuilding the utility internally.

Look elsewhere when:

• You are building or maintaining a modern Laravel application.
• You need PHP 8+ compatibility, active maintenance, security patches, or framework integration.
• You require community validation, documented support, or long-term dependency viability.
• The package would become part of a customer-facing or revenue-critical path.

How to Pitch It (Stakeholders)

Executive summary: orkestra/common is not a viable dependency for new product work. It is an old Doctrine 2 utility package with negligible adoption, no dependents, and no releases since 2014. Adopting it would create maintenance and security exposure without meaningful strategic or feature value.

For engineering: Avoid adding this package to Laravel applications. If a legacy Doctrine 2 system already uses it, isolate it, document the risk, and plan replacement or internal ownership. For modern builds, implement the small utility internally or choose actively maintained, Laravel-compatible alternatives.

Recommendation: Do not adopt. Treat it as a legacy-reference package only, and use it to reinforce dependency-review criteria rather than as a build-vs-buy candidate.