- Can I use sbyaute/star-rating-bundle in a Laravel application?
- Not natively. sbyaute/star-rating-bundle is a Symfony bundle built around a Bundle subclass, a DI extension, and Twig templates, none of which Laravel uses. Installing it into a Laravel app is technically harmless but leaves an uninvoked bundle class and adds a dead dependency. Treat it as a reference implementation and port the star markup and CSS into a Blade component instead.
- How do I install sbyaute/star-rating-bundle with Composer?
- You would run composer require sbyaute/star-rating-bundle, but in a Laravel project that only adds the package without any Laravel auto-discovery, service provider, or Blade views. There is no Laravel integration to register, so installation gives you nothing at runtime. If you want the assets, vendor the template and stylesheet with an MIT attribution header rather than adding the dependency to composer.json.
- Does sbyaute/star-rating-bundle support Laravel 10 or Laravel 11?
- There is no declared Laravel version support. The package targets Symfony with Twig templates and does not publish Laravel constraints or framework integration. Its last release was January 2023, with no signal of PHP or Laravel version tracking since then. Do not assume compatibility with current Laravel releases.
- Is sbyaute/star-rating-bundle actively maintained?
- The evaluation found 0 GitHub stars, 0 dependents, and a single maintainer, with the last release in January 2023. There is no evidence of production use, security triage, or ongoing PHP and Laravel version tracking. The MIT license is permissive and low-risk for vendoring with attribution, but the project itself shows little maintenance activity.
- What features does the star rating bundle provide?
- It provides configurable star counts, colors, sizes, and half-star support, plus a read-only display mode and interactive voting with hover previews. It also exposes aggregate scores and vote counts for templating, and uses lightweight dependency-free markup with ARIA accessibility claims. The core is framework-agnostic, with simple service and template integration around it.
- How do I port the Symfony Twig star rating widget to Laravel Blade?
- Translate the Twig template into an anonymous Blade component such as x-star-rating with value and max props, and move the clamping or rounding logic into the component class or a small helper. Copy the framework-agnostic CSS into resources/css and wrap any interactive JavaScript in Alpine or Livewire if that is your stack. Leave the Symfony Bundle class, DependencyInjection extension, and YAML config behind because they do not transfer to Laravel.
- Does sbyaute/star-rating-bundle store votes or is it display only?
- That is not confirmed by the package description, which suggests a presentational star rating widget rather than a persistence layer. The technical evaluation explicitly flags whether the repository contains persistence, aggregation, or moderation logic as unresolved. Before committing engineering time, audit the repository to confirm the actual code surface. Assume you will build vote storage and aggregation yourself in Laravel.
- Is the star rating markup from this bundle accessible?
- The package description claims ARIA accessibility and dependency-free markup, but that should be audited rather than trusted. Check for aria-label usage, a role of img or equivalent, keyboard operability, and color contrast ratios in the interactive mode. The evaluation warns that you may inherit accessibility debt if the widget only supports mouse hover. Verify the markup before adopting it into a design system.
- What are the alternatives to using a Symfony bundle for star ratings in Laravel?
- Build a small Blade component or a Livewire or Alpine component, since the useful surface here is just star markup, CSS, and optional hover behavior. Laravel-friendly rating packages or your own design-system component avoid the dead dependency and give you control over accessibility and persistence. Because the bundle's Symfony plumbing does not transfer, reimplementation is usually the lower-risk path.
- How much effort is it to reimplement this star rating widget in Laravel?
- The evaluation estimates a few dozen lines of Blade plus a small stylesheet, or roughly half a day for one frontend engineer. The reusable parts are the star markup template, the CSS, any small JavaScript for hover behavior, and a trivial helper for clamping or rounding a rating value. If you can reproduce the entire useful surface in under a day, the dependency question is settled in favor of building it yourself.