Sharethis Widget Laravel Package

Product Decisions This Supports

• Build vs. buy for social sharing UI: This package is effectively a build artifact — a thin Symfony/Victoire wrapper that renders ShareThis embed markup as a page-builder widget. Its real value to a PM is as a reference for how cheap this feature is to build in-house (a Twig template plus a widget service definition), not as a dependency to purchase or adopt.
• Roadmap scoping for CMS page-builder widgets: If you operate a widget-based CMS, this clarifies that "add ShareThis buttons" is a sub-day task, not an epic. It should never occupy roadmap capacity beyond a backlog line item.
• Feature parity triage: Useful only as a checklist item when auditing whether your CMS exposes social-share blocks alongside other content widgets. Absence of a share widget is a minor gap, not a differentiator.
• Vendor dependency policy: Given ShareThis itself is a third-party script, the decision that matters is "do we ship a third-party social script at all" (privacy, GDPR consent, page-weight, CSP implications) — not "which wrapper package do we use."
• Explicitly not a Laravel decision: Despite being surfaced in a PHP package evaluation, this is a Symfony bundle for Victoire DCMS (FriendsOfVictoire/WidgetShareThisBundle). If your stack is Laravel, this package answers no question you have — do not let it enter a Laravel dependency review.

When to Consider This Package

Consider it only under a narrow, mostly historical set of conditions:

• You are running Victoire DCMS on Symfony and want the smallest possible path to a ShareThis widget in the page builder.
• You need a reference implementation for registering a third-party embed as a Victoire widget — read the source, don't depend on it.
• You are maintaining a legacy Symfony 2/3 application already pinned to Victoire-era components and cannot modernize the sharing block independently.

Look elsewhere — or build — in essentially every other case:

• Wrong framework. Not Laravel, not framework-agnostic. Zero applicability to Laravel, and mixing Symfony bundles into a Laravel app is a non-starter.
• Zero adoption signal. 1 star, 0 dependents, no downstream consumers to inherit bug fixes or compatibility guarantees from.
• Unmaintained since 2016-11-16. Nearly a decade without a release. No PHP 8 compatibility, no Symfony 5/6/7 support, no security response path, and ShareThis's own embed format has changed since. The overall health score (~0.095) confirms this.
• The functionality is trivial. ShareThis publishes a copy-paste JS snippet; recreating this in any templating engine is an hour of work with full control over consent gating, CSP, and lazy loading — none of which this wrapper addresses.
• Privacy/compliance surface. No evidence of consent-management integration; shipping a 2016-era third-party script wrapper into a modern product invites GDPR/CCPA review debt.

Recommendation: do not adopt. Build the snippet in-house (or use ShareThis's current official embed) and treat this repo as documentation only.

How to Pitch It (Stakeholders)

For executives (one paragraph): We evaluated friendsofvictoire/sharethis-widget as a candidate for adding social-share buttons and are recommending against adoption. It is a Symfony bundle for the Victoire CMS — not usable in our Laravel stack — with a single star, no dependent projects, and no release since November 2016. Taking it on would import an unmaintained, unpatched dependency for functionality we can implement ourselves in under a day. The real decision on the table isn't "which package," it's "do we want a third-party social script on our pages at all," which carries privacy-consent and page-performance implications we should decide deliberately. Net: no cost avoided, new risk introduced.

For engineering (summary): This is a ~one-widget Symfony bundle that wires ShareThis embed markup into Victoire's page-builder registry. It is not a Laravel package and has no Laravel integration path. It is unmaintained since 2016 — no PHP 8 or modern Symfony support, no security update channel, and zero dependents. Do not add it as a dependency. If we want share buttons, implement natively: a template partial with the current ShareThis (or equivalent) snippet, gated behind our consent mechanism, loaded lazily, and covered by a CSP allowance. Estimated effort: well under a day. If we need a pattern for "register a third-party embed as a widget," skim the repo's source for structure and move on.