Product Decisions This Supports
- Legacy platform triage: Helps decide whether an existing eZ Publish 5 (eZ5) installation should be kept on life support, frozen, or scheduled for re-platforming — this bundle only exists to serve that legacy stack.
- Content model / migration scoping: If the xrowVideo custom datatype is in the content model, this package defines what "video content" looks like in the old system and therefore what must be mapped, normalized, or dropped during a migration to Ibexa DXP, a headless CMS, or a modern framework.
- Build vs. buy vs. reuse for video embedding: Informs the decision to keep a bespoke datatype wrapper versus replacing it with standard oEmbed/embed-field or a third-party video platform integration — the package is a candidate for "replace," not "buy."
- Roadmap risk inventory: Flags a deprecated, unmaintained dependency (last release 2016, 0 stars, 0 dependents) so it can be logged as technical debt with an owner and a retirement date rather than silently persisting.
- Maintenance investment decision: Supports the call on whether to fork/patch the bundle in-house (only if a legacy site must stay up) versus accepting functional freeze.
- Not a fit for: any greenfield Laravel or modern PHP initiative — this is a Symfony bundle for eZ5, not a Laravel package, so it should not enter new-build evaluations.
When to Consider This Package
Consider only if all of the following hold:
- You are maintaining an existing eZ Publish 5 application that already uses the custom
xrowVideo datatype in stored content.
- Content editors or front-end templates depend on that datatype's rendering behavior today.
- A migration or re-platform is not funded in the current planning horizon, and you need continuity rather than improvement.
- You have PHP/engineering capacity to own and patch the code yourselves, since upstream is inactive.
Look elsewhere when:
- The project is Laravel, Symfony 6+/7, or any framework not pinned to the eZ5 era — the package will not integrate.
- You need modern video capabilities: oEmbed resolution, responsive players, accessibility, CSP/consent handling, CDN or streaming platform integration.
- You are evaluating for a new build, a proof of concept, or a vendor selection matrix — zero stars and zero dependents mean no community, no security response, and no support path.
- Your security or dependency policy prohibits packages marked deprecated with no release since 2016.
- You are planning an Ibexa DXP upgrade — use Ibexa's supported field types and migration tooling instead of carrying this bundle forward.
Practical caution: verify PHP version compatibility and licensing before any use; expect to vendor the code and treat it as internal, unsupported software.
How to Pitch It (Stakeholders)
For executives: This is a deprecated legacy component from 2016 that exists solely to keep custom video content working on an old eZ Publish 5 site. It is not a strategic investment and carries no vendor support or community backing. It is not a risk we need to act on immediately, but it should be recorded as technical debt and addressed as part of any re-platforming decision — every quarter we stay on the legacy stack extends our exposure.
For engineering: It is a thin eZ5 compatibility bundle for the xrowVideo datatype. There is no active maintenance, no dependents, and no release in roughly a decade. Treat it as frozen internal code: pin the version, vendor it if the site must remain live, and avoid extending it. Any new video functionality should be built on standard embed/oEmbed patterns in the target platform, not on this bundle.
Recommendation: Do not adopt. Preserve only where a live legacy site requires it, assign an internal owner, and prioritize content migration so the dependency can be retired.