Weave Code
Voting Bundle Laravel Package
kunstmaan/voting-bundle
KunstmaanVotingBundle adds reusable voting and rating features to Symfony applications, including entities, services, and templates for casting and tallying votes. Lightweight but low-maintenance; verify compatibility before use.
KunstmaanVotingBundle adds flexible up- and down-voting to Symfony applications. Votes are stored as Doctrine entities and dispatched through events, letting you plug in custom logic—such as blocking duplicate votes or updating counters—without modifying the bundle itself.
- Doctrine ORM entities and repositories for persisting votes
- Event-driven vote handlers for validation and side effects
- Multiple vote types per object (e.g. upvote/downvote)
- Simple service API for casting and querying votes
- Twig helpers for rendering vote controls
Frequently asked questions about Voting Bundle
- Is kunstmaan/voting-bundle a Laravel package?
- No. kunstmaan/voting-bundle is a Symfony bundle from the Kunstmaan CMS ecosystem, distributed as a read-only subtree split. It is not a native Laravel package and does not use Laravel service providers, Eloquent, or Laravel conventions. Treat it as a domain reference rather than a drop-in Laravel dependency.
- Can I install kunstmaan/voting-bundle in a Laravel application?
- Direct installation is not recommended. The bundle assumes Symfony bundle wiring, Doctrine mappings, and legacy service configuration that do not map cleanly onto Laravel's container or Eloquent models. You could attempt a bridge, but the integration risk is high and the package is effectively abandoned.
- What does kunstmaan/voting-bundle actually provide?
- It provides vote entities and services for recording, counting, and managing votes on objects, plus campaign-related concepts such as deadlines, social-network votes, and irregularity review. That makes it useful as a blueprint for like/dislike or simple rating features. It is not a modern, framework-agnostic voting library.
- Which Laravel and PHP versions are supported by kunstmaan/voting-bundle?
- There is no Laravel version support because it is a Symfony bundle. The last release dates from 2014, so you should assume incompatibility with modern Laravel, PHP 8+, and Symfony 6 or 7. Composer resolution, Doctrine mapping, and old bundle configuration are likely blockers.
- Is kunstmaan/voting-bundle still maintained?
- No, it is effectively unsupported. The last release was in 2014, with minimal adoption and no dependents, so your team would own all fixes, security patches, and compatibility work. For a production system, that is a build-and-own decision, not a normal dependency choice.
- How should I implement like/dislike or rating voting in Laravel instead?
- Extract the useful domain concepts and rebuild them natively with Laravel migrations, Eloquent models, policies, queues, and scheduled commands. Define explicit models such as Campaign, Vote, VoterIdentity, FraudSignal, and CampaignDeadline. Add idempotency rules and unique constraints early so duplicate votes are prevented at the database level.
- What are the security and fraud risks of using this bundle?
- The main risks include duplicate voting, weak voter identity handling, vote fraud, campaign deadline edge cases, and outdated social API assumptions. A 2014 package is unlikely to satisfy modern anti-fraud, audit, privacy, and retention requirements out of the box. Run a threat model and security review before considering any reuse.
- Can I use kunstmaan/voting-bundle for Facebook or social network votes?
- Not safely. Social-network integration is the riskiest part because Facebook APIs, permissions, and OAuth flows have changed materially since 2014. Treat any social voting code as historical reference only, and build new provider adapters after confirming current API feasibility. For Laravel, use maintained OAuth and socialite-style integrations instead.
- How would I migrate from kunstmaan/voting-bundle to a Laravel voting module?
- Start with a time-boxed spike to document the bundle's entities and workflows, then map them to current requirements. If a legacy Symfony system already uses it, isolate the bundle behind an adapter and plan a phased replacement. Rebuild the vote data model, campaign lifecycle, deadline enforcement, anti-fraud logging, and reporting natively in Laravel.
- What alternatives should I consider for Laravel voting or campaign features?
- Consider building a small internal voting module with Laravel's own models, policies, queues, and scheduled commands, or evaluating maintained Laravel packages for ratings and reactions. The Kunstmaan bundle is MIT licensed, so copying isolated concepts is possible, but provenance and security review are still required. Avoid making it a production dependency in a modern Laravel stack.
Weaver
How can I help you explore Laravel packages today?