Share Buttons Bundle Laravel Package

Product Decisions This Supports

• Build vs. reuse for a narrow, low-differentiation feature. Share buttons are commodity UI; this package answers "can we ship social sharing in a sprint instead of a story point estimate?" That is its only real value proposition.
• Legacy platform triage. If you are still operating eZ Publish 5.x / eZ Platform on Symfony 2.x–3.x, this is one of the few first-party eZ Systems bundles that slots in via AppKernel/EzPublishKernel with per-siteaccess YAML config. It informs a keep-the-lights-on decision, not a roadmap bet.
• Editorial/content-marketing use cases. The per-siteaccess provider toggles map well to multi-brand or multi-locale content sites where different editorial teams want different networks (Facebook, X, LinkedIn, etc.) without code changes.
• Scope-shaping signal — weak, use with caution. 5 stars, 0 dependents, no release since Feb 2018, and archived status mean there is essentially no market validation. Treat this as "one team's internal utility that escaped," not as evidence of a category need. Do not let it anchor a build/buy narrative.
• What it should not decide: anything about analytics instrumentation (UTM/campaign attribution), privacy/consent architecture, or personalization. The package is presentation-layer only; those decisions belong to your tag manager and CMP.
• Deprecation/exit planning. It usefully forces the question "what is our replacement path for Assetic-based Twig assets and Symfony 2-era bundles?" — a roadmap input in its own right.

When to Consider This Package

Consider it only when all of these hold:

• You are on eZ Publish 5.x or eZ Platform (Symfony 2.6–3.x) and cannot upgrade the host application independently of this feature.
• The requirement is genuinely just "render share links + optional default CSS" — no tracking, no consent gating, no accessibility mandate beyond the template.
• You can vendor/fork it internally and accept ownership of maintenance, including security review of a 2018 codebase.
• Legal has cleared the license: the repository reports NOASSERTION, which means the license could not be automatically identified. Until a human reads the LICENSE/headers, assume you cannot ship it.
• Time-to-market dominates; the feature is not customer-facing-differentiated.

Look elsewhere (or build in-house) when:

• You are on Symfony 4+/5+/6+/7 — the Assetic {% stylesheets %} pattern and the bundle's Symfony 2.6 floor make this a poor fit; Assetic itself is unmaintained.
• Archived = no security patches. Share buttons are an XSS/third-party-script surface; an unmaintained package here is a real risk, not a theoretical one.
• You need privacy/consent compliance (GDPR/ePrivacy): third-party share endpoints and vendor JS can set cookies or leak referrer data. This bundle gives you no consent hooks.
• You need analytics-grade output — UTM construction, share-event tracking, canonical URL/Open Graph consistency — none of which is in scope here.
• You need a maintained vendor relationship. eZ Systems is now Ibexa; this bundle is not part of the supported product surface.

Pragmatic alternative to put in front of engineering: a ~100-line Twig partial plus a small config map of provider → share URL is functionally equivalent, has no abandoned dependency, and is trivially auditable. The bundle's entire value is the config/template plumbing you could reproduce in an afternoon.

How to Pitch It (Stakeholders)

To executives (30 seconds): This is a small, abandoned third-party add-on that renders social sharing links inside our legacy eZ Platform CMS. It solves a commodity problem, it has zero adoption in the wild, it has not been touched since 2018, and its license is unverified. Recommendation: no new adoption. We should not add it to any current or planned product. If we already have it in a legacy deployment, it belongs on the technical-debt register with a low-cost replacement (a small in-house template component) scheduled opportunistically — not a project.

To engineering (the real decision): The only scenario where this is defensible is a Symfony 2.6–3.x eZ Platform site where we need configured-per-siteaccess share links this sprint. In that case: fork it, pin the commit, verify the license, review the templates for escaping, and treat the fork as our code. Otherwise, replace it — the Assetic asset include, the missing maintainer, and the archived status are all future incidents waiting to happen, and the replacement cost is measured in hours, not sprints.

Ask: 1) Confirm whether any live site depends on this bundle. 2) If yes, fund a small spike to replace it with an owned Twig partial. 3) If no, close it out and record the decision so it doesn't resurface as a "quick win" suggestion.