Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Poll Bundle

Poll Bundle Laravel Package

prism/poll-bundle

Prism Poll Bundle brings simple polling to Laravel apps, letting you create polls, add options, collect votes, and display results through a lightweight API and Blade-friendly views. A practical choice for adding community polls or quick surveys.

View on GitHub
Deep Wiki
Context7

At a glance

Frequently asked questions about Poll Bundle
Is prism/poll-bundle a Laravel package?
No. Prism Poll Bundle is a Symfony 2 bundle, not a Laravel package. Its value is mostly framework wiring: AppKernel registration, DI container service definitions, bundle routing config, and Twig templates. There is no portable domain layer you can lift into a Laravel service provider without effectively rewriting it.
Does prism/poll-bundle work with Laravel 10 or 11?
No. There is no Laravel service provider, no Laravel migrations, and the underlying Symfony 2 framework reached end of life in 2018. Composer will almost certainly refuse to resolve the package's framework and PHP constraints against a supported Laravel runtime. The realistic path is a fork-and-port, not an install.
How do I install prism/poll-bundle?
Historically you installed it with Composer inside a Symfony 2 application, registered the bundle in AppKernel, imported its config and routing, then updated the schema. That workflow does not exist for Laravel. For a Laravel target, treat the repository as a reference spec and reimplement the poll domain, or fork and port it deliberately.
Is prism/poll-bundle still maintained?
There is no sign of an active maintainer, CI pipeline, or release cadence. Symfony 2 has been end of life since 2018, and the package shows roughly 19 stars with zero dependents. Treat it as abandoned: no upstream fixes, no security patching, and no compatibility work for current PHP or framework versions.
Does prism/poll-bundle prevent duplicate votes and ballot stuffing?
The vote-integrity model is one of the key open questions: it is unclear whether deduplication is anonymous, session-based, IP-based, or tied to authenticated users. A bundle of this vintage is unlikely to meet current expectations for CSRF protection, input validation, and duplicate-vote guards. Because polling is user-generated write traffic, review this carefully before exposing it in production.
What should I use instead of prism/poll-bundle in Laravel?
Prefer a maintained Laravel package with real dependents and an active release history, or build the feature in-house. The domain is small: a Poll model, a PollOption model, a Vote model, migrations, a tally query, and a thin controller and policy layer. That is a days-scale task and removes the framework coupling and EOL dependency in one step.
How hard is it to port prism/poll-bundle to Laravel?
It is days-scale work, not weeks-scale work. Translate the Symfony entities into Eloquent models with migrations, add a controller and policy layer, and replicate the tally logic and Blade-friendly views. Using the original repo as a spec for the data model and UX flow is the fastest reliable route.
Can I install prism/poll-bundle on PHP 8?
Almost certainly not, since the package is from the Symfony 2 era and its PHP constraint will not match modern runtimes. Check the exact composer.json constraints for PHP, Symfony, Twig, and Doctrine ORM before attempting anything. Assume those constraints block modern installs until proven otherwise.
Is prism/poll-bundle safe for production use?
Abandonment risk is high: there are no upstream security fixes and no compatibility work. Current defaults for CSRF protection, output escaping, input validation, and vote integrity are unlikely to be met. For a small, easily rebuilt feature, the risk outweighs the value, so production use is not recommended.
Does prism/poll-bundle have tests or CI history?
There is no evidence of a test suite or CI history, which suggests a demo-grade repository. With roughly 19 stars and zero dependents, no downstream project has validated the code path you would exercise. Any fork would need its own test coverage and security review before you rely on it.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core
nodisrupt/laravel-agent
sierratecnologia/media-manager