Weave Code
Shariff Bundle Laravel Package
nucleos/shariff-bundle
Symfony bundle that integrates Shariff, the privacy-friendly social sharing buttons. Adds share buttons for popular networks without tracking users, with configurable services, templates, and styling. Easy to install and customize for Symfony applications.
This bundle provides shariff integration in symfony applications
Frequently asked questions about Shariff Bundle
- Can I install nucleos/shariff-bundle in a Laravel app?
- No, not as a working dependency. It is a Symfony bundle that ships a DependencyInjection extension with a Configuration tree, container service definitions, a Twig extension, and a controller route for the Shariff share-count endpoint. Laravel has no bundle or container-extension equivalent, so Composer requiring it will not just work. Any Laravel use is a reimplementation of its responsibilities, not an installation.
- What does nucleos/shariff-bundle actually do?
- It is a thin Symfony adapter over the heise/shariff PHP library. It registers the Shariff backend service, exposes a share-count endpoint, provides configuration for enabled networks, and injects the frontend assets. Shariff renders share buttons client-side and proxies counts server-side so visitors' browsers never contact Facebook or X directly. The genuinely reusable value is small: a service list, a route, and a Twig or Blade partial.
- Is nucleos/shariff-bundle still maintained?
- No. The repository is archived, the last release was December 2021, and it has four stars, zero dependents, and no issue triage. There are no security patches and no community to absorb maintenance. Treat it as an abandoned single-author artifact.
- Does nucleos/shariff-bundle support Laravel 10 or 11 and PHP 8.2+?
- No. It is a Symfony bundle and has no Laravel integration of any kind. It also has no PHP 8.2, 8.3, or 8.4 support commitments and no Symfony 6 or 7 alignment. With a December 2021 last release, it should be considered unsupported for modern stacks.
- How do I add privacy-friendly social share buttons in Laravel?
- Vendor Shariff's static JS and CSS assets and render the buttons from a Blade component; no PHP package is required for buttons-only use. If share counts are needed, add a small Laravel controller that proxies requests through the heise/shariff backend, put a cache layer in front of it, and register the route in a service provider. This gives you code your team owns outright in roughly a day or two.
- Do I need server-side share counts, or only Shariff buttons?
- If you only need privacy-friendly share buttons, the static Shariff JS and CSS assets require no PHP package at all, and the entire integration question disappears. Server-side counts are the volatile part: X/Twitter removed public count access and Facebook has repeatedly restricted unauthenticated counting. Decide scope first, because dropping counts eliminates roughly half the work.
- How would I configure a Laravel-native Shariff integration?
- A Laravel-native equivalent needs a config file listing enabled networks, one controller action proxying count requests through the heise/shariff backend, a cache layer, a Blade component that emits the Shariff markup and loads the static assets, and a route registration in a small service provider. That is a day or two of work and yields code you own outright. It avoids adopting an abandoned Symfony bundle.
- Which networks still provide share counts for Shariff buttons?
- Fewer than you might expect. X/Twitter removed public count access and Facebook has repeatedly restricted unauthenticated counting, while Reddit and others have changed terms. A Shariff deployment built in 2021 will have several dead or rate-limited backends today regardless of the wrapper's health. Check each network's current API terms before promising share counts to stakeholders.
- How should I test and deploy privacy-friendly share buttons in production?
- Verify that no third-party requests fire before consent by inspecting the network tab, and test the count endpoint with caching enabled so rate limits do not break the page. There is no maintained test suite or production evidence for this bundle, so any adoption means owning testing yourself. Prefer static assets plus a small in-house endpoint you can monitor and cache.
- What are the best alternatives to nucleos/shariff-bundle for Laravel?
- The realistic alternatives are upstream Shariff static JS and CSS assets with a Blade component, consent-gated native share buttons, or a small in-house Laravel endpoint if counts are truly required. There is no maintained Laravel package equivalent in this repository. For Laravel, a small in-house implementation is cheaper than forking and owning this bundle indefinitely.
Weaver
How can I help you explore Laravel packages today?