- Can I install nurikabe/star-rating-bundle in a Laravel application with Composer?
- Not practically. Despite being catalogued as a Laravel/PHP package, it is a Symfony bundle whose code depends on Symfony kernel registration, a DI extension, a Symfony FormType, and Twig. Composer will likely fail to resolve against a modern Laravel app because of its Symfony 2.x-era constraints and PHP requirements, and forcing it with --ignore-platform-reqs only poisons your lockfile. Treat the repository as reference material rather than a dependency.
- What does Nurikabe StarRatingBundle actually provide?
- It provides configurable star-rating controls and displays for Symfony applications, exposed through Twig helpers. Internally it is mostly Symfony glue: a bundle class, a dependency-injection extension for service and config wiring, a FormType, and a Twig extension that renders the markup. The only portable pieces are the underlying JavaScript star-rating widget and the HTML/CSS conventions it emits.
- Why is this Symfony bundle listed as a Laravel package?
- It appears to be a cataloguing error in the package index rather than a genuine Laravel integration. The architecture is Symfony-specific by construction, with no Blade, Eloquent, service provider, or Laravel validation surface. Roughly 90 percent of the code is Symfony glue that is dead weight in a Laravel context.
- Does StarRatingBundle support Laravel 10, Laravel 11, or PHP 8.2?
- No. The bundle has been unmaintained since April 2015, predating modern PHP and Laravel entirely, and there has been no PHP 8 compatibility work or Composer constraint updates. Symfony 2.x-era code routinely fails on modern PHP due to removed functions, signature changes, and deprecated patterns. There is no Laravel version support to speak of at any release.
- What is the best way to add star ratings to a Laravel app instead?
- Adopt a maintained alternative rather than integrating this package. For display-only ratings, an inline SVG or CSS-only partial with aria-label and a width-based clip for fractional stars is a few lines of markup. For input, a small Alpine.js component or a Livewire rating property backed by a hidden input covers the use case in roughly 40 lines with zero legacy surface.
- Can I reuse the JavaScript star-rating widget from this bundle with Vite?
- Yes, but only as a manual extraction. Copy the widget into resources/js/vendor, register it in your Vite or Mix pipeline, and rebuild the server-side surface as a Blade or Livewire component plus a validation rule and an Eloquent column convention. That is a rewrite of the integration layer, not an install. Keep in mind the widget is a jQuery-era plugin frozen in 2015.
- Does this star rating package require jQuery?
- The bundle targets a Symfony 2.x stack and wraps a client-side widget from the jQuery era, so a jQuery dependency is effectively implied. That is a friction point in a modern Laravel app built on Vite with no jQuery in the stack. If you extract the widget, budget time for auditing it against current browser and security expectations.
- Is Nurikabe StarRatingBundle still maintained?
- No. The last release dates to 2015-04-10, with no security patches, no PHP 8 work, and no dependency updates since. It has roughly 10 stars and 0 dependents, which means essentially no community scrutiny. There is also no evidence of a test suite, CI pipeline, or security review in the repository.
- Is it safe to use this abandoned package in production?
- Treat it as suspect. The security surface is small but real: XSS risk from unescaped label or title strings in the rendering helper, plus stale jQuery CVEs in the client-side widget. Because the project is unmaintained, any fork you create becomes your own unaudited code. For a display-only rating, the risk is not worth it when a CSS or SVG partial does the job.
- What licensing issues should I check before forking StarRatingBundle for Laravel?
- The bundle is a wrapper around a third-party widget, and the wrapper and upstream widget may carry different licenses. Confirm both before vendoring or forking, and make sure your organisation has an approved path for adopting abandoned code. Attribution requirements from the original widget should be preserved in whatever you ship.