Xrowmetadata Bundle Laravel Package

Product Decisions This Supports

• Legacy platform triage: Informs whether to keep patching an eZ Publish 5 (eZ5) installation or fund a migration. This bundle only addresses a narrow legacy datatype problem, so it is a signal to assess the broader platform lifecycle.
• Build vs. buy vs. migrate: The “buy” option is effectively unavailable—the package is deprecated, unmaintained since 2017, and has no visible adoption. The real decision becomes “fork/patch internally” versus “migrate off eZ5.”
• Roadmap risk scoring: Zero stars, zero dependents, and a deprecated label mean this should be treated as technical debt, not a strategic dependency. It should not enter a modernization roadmap except as a temporary compatibility shim.
• Content model and datatype audits: If product/content teams still rely on xrowMetadata custom datatypes, this package surfaces a dependency that must be inventoried before any CMS upgrade or re-platforming.
• Maintenance budgeting: Supports deciding whether to allocate engineering time to vendor/fork a tiny abandoned bundle or to accelerate migration away from the legacy stack.

When to Consider This Package

Consider it only when all of the following are true:

• You are maintaining an eZ Publish 5 / eZ5 application, not a Laravel or modern PHP application.
• The content model uses the xrowMetadata custom datatype and the installation depends on the xrow datatype registration/fix this bundle provides.
• You need a short-term compatibility bridge while planning migration, and you are prepared to pin, vendor, or fork the code.
• You have audited the code and are comfortable accepting that it is deprecated, has no active maintainers, no releases since 2017, and no measurable community adoption.

Look elsewhere when:

• You are building or maintaining a Laravel application—this is a Symfony/eZ5 bundle and is not applicable.
• You are on eZ Platform / Ibexa or a modern CMS; this is legacy eZ5-specific.
• You need security patches, long-term support, or a supported vendor relationship.
• You do not specifically depend on xrowMetadata; the bundle adds no general value.
• You can migrate the content model or replace the custom datatype instead of carrying the dependency forward.

How to Pitch It (Stakeholders)

Executive summary: This package is a deprecated, unmaintained compatibility fix for a custom datatype on the legacy eZ Publish 5 platform. It has no meaningful adoption—zero stars and zero dependents—and no release since 2017. It should not be treated as a viable long-term dependency.

For engineering: The bundle is narrowly scoped to fixing xrowMetadata datatype behavior on eZ5. If we still run that stack and use that datatype, we can vendor or fork it as a temporary bridge, but we must pin the version, document ownership, and include it in migration planning. It is not a Laravel package and offers no value outside legacy eZ5.

Recommendation: Do not adopt this for new work. If it is already in a legacy system, treat it as technical debt: confirm whether xrowMetadata is still required, evaluate removing or replacing the custom datatype, and fund migration away from eZ5 rather than investing in an abandoned bundle.