Sonata Admin Splash Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy for sync observability: Informs whether a sync-status/explorer UI in an admin panel is worth building in-house or is adequately covered by an ecosystem plugin. This bundle represents the "buy/borrow" option: a read-only explorer surface for Splash Sync inside Sonata Admin.
• Admin-console roadmap: If your product plan includes a "connections & sync health" screen for operators (last sync, mapping, queue status), this package is a reference pattern for what such a panel minimally contains — not a component to ship.
• Vendor/stack validation: Serves as a data point in evaluating Splash Sync as a synchronization backbone alongside Sonata Admin. Its archival status is itself a signal about the maturity and maintenance of that integration path.
• Feature scoping: Clarifies the boundary between "explorer" (read-only inspection of sync objects/config) and "operator controls" (retry, pause, re-map). If your roadmap needs the latter, this bundle is out of scope by design.
• Deprecation/technical-debt triage: If any legacy deployment already depends on it, this assessment supports a decision to migrate off rather than extend.

When to Consider This Package

Consider only in narrow, constrained situations:

• You are already running Sonata Admin and Splash Sync in an existing app, and you want a quick read-only explorer for sync objects without writing the admin CRUD yourself.
• You are prototyping or doing a feasibility spike and need a UI surface to demonstrate sync state to stakeholders within days.
• You are doing archaeology on a legacy codebase and need to understand what an inherited Splash/Sonata integration was doing.
• You want to read the source as a reference implementation for how to wire a Splash Sync explorer into a Symfony/Sonata admin — not to install it.

Look elsewhere — or build — if any of the following are true:

• Maintenance and security matter. The repository is archived, has 1 star, 0 dependents, and no license concerns (MIT) but also no security patching, no Symfony/PHP version support guarantees, and no issue triage. Treat it as frozen code.
• You need write operations, alerting, retries, or sync orchestration — this is an explorer, not an operations console.
• Your stack is not Sonata Admin (e.g., EasyAdmin, custom admin SPA, Laravel Nova/Filament-style panels). The bundle's value is inseparable from Sonata.
• You are on a modern Symfony/PHP version — an archived bundle's dependency constraints will likely conflict, and Composer resolution alone may block adoption.
• You need vendor support or an SLA for a production sync pipeline.

How to Pitch It (Stakeholders)

For executives: This is a small, archived integration plugin that adds a read-only "sync explorer" screen to the Sonata Admin back office for Splash Sync users. It is not a strategic asset: one star, zero dependent projects, and the repository is archived — meaning nobody is maintaining it. We should not build a roadmap dependency on it. The useful takeaway is directional: it shows what a sync-visibility panel looks like, which informs our own admin-console planning. Recommendation: do not adopt; use as a reference pattern only.

For engineering: If an existing app already uses it, plan to replace it with a thin, in-house admin screen backed by the Splash API/SDK, since archived bundles become version-locked liabilities at the next framework upgrade. If we are greenfield, the cost of a minimal read-only explorer (list sync objects, show status, link to logs) is low enough that owning it is cheaper than inheriting an unmaintained dependency. Confirm Sonata Admin and Splash Sync are actually in our stack before spending any further cycles — otherwise this is a non-decision.