- What is the laravelsurveyjs package used for?
- It is a deprecated Laravel wrapper for SurveyJS, the client-side survey and form engine. It provides a service provider, publishable config and migrations, Survey models, controllers for storing responses and answers, and a Blade include that loads SurveyJS assets. You use it to render JSON-defined surveys and persist submissions in a Laravel monolith without writing that scaffolding yourself.
- Is aidynmakhataev/laravelsurveyjs still maintained?
- No. The package is marked deprecated, its last release was 2021-05-27, and the evaluation notes no evidence of a maintainer response SLA. With 82 stars and zero dependents, adopting it means becoming the de facto maintainer. Treat it as a reference implementation rather than an actively maintained dependency.
- Does laravelsurveyjs support Laravel 10, 11, or 12 and PHP 8.2/8.3?
- There is no evidence that it does. It was authored against Laravel 8-era conventions and PHP constraints from that period, and the evaluation expects Blade syntax, config publishing, and tests to be unexercised on newer versions. Auto-discovery may work, but you should expect to fork and widen the composer.json constraints for Laravel 10, 11, or 12 and PHP 8.2 or 8.3.
- How do I install and configure laravelsurveyjs in a Laravel app?
- Install it with Composer, then publish the package config and migrations and run migrations to create the survey and response tables. The package includes a service provider and a Blade include that adds the bundled SurveyJS JavaScript and CSS to your page. Because the package is deprecated and old, spike the install on a throwaway branch and verify the published assets and routes against your Laravel version first.
- How does laravelsurveyjs store survey definitions and responses?
- It ships models, migrations, and controllers for surveys, pages, questions, and responses, with SurveyJS definitions stored as JSON and mapped through Eloquent casts. The controller persists submissions into responses and answers tables. This JSON-column approach fits the fact that SurveyJS forms are defined as JSON, but the evaluation flags schema drift as a data-lifecycle risk for long-lived stored definitions.
- Can I use laravelsurveyjs with Inertia, React, Vue, or an API-first frontend?
- Not usefully. The wrapper's value is Laravel-side glue for Blade or Livewire monoliths: service provider, migrations, Survey model, submission controller, and a Blade asset include. In an Inertia, React, Vue, or API-first app you would install the official survey-core and survey-creator-core npm packages and write your own two endpoints instead. The wrapper contributes almost nothing in that architecture.
- Which SurveyJS version does the package bundle, and can I upgrade it?
- The evaluation says the bundled SurveyJS assets will be several major versions behind current SurveyJS, which creates both functional and patch-level security gaps. It also notes that swapping the front-end assets may be possible independently, but doing so invalidates the just-install-it value proposition. Check the vendored files and test whether you can replace them without touching package code before relying on this wrapper.
- Is laravelsurveyjs safe to use in production?
- Treat it as high risk. The license is reported as NOASSERTION, meaning GitHub could not match an SPDX license, which for a commercial product may mean no grant to use, modify, or redistribute, so legal review is a hard gate. The package is also deprecated, has had no release since 2021, has zero dependents, and its server-side validation behavior is unclear from the evaluation.
- Does laravelsurveyjs validate survey responses on the server?
- The provided evaluation does not establish that it does. One of its key spike questions is whether responses are validated server-side or whether the package trusts the client, along with whether it handles multi-tenancy, survey-definition versioning, and partial or incomplete submissions. Do not assume validation; inspect the controller and add your own Laravel validation rules if you proceed.
- What are the alternatives to laravelsurveyjs for building surveys in Laravel?
- For a modern Laravel app, the lower-risk path is to use the official SurveyJS npm packages survey-core and survey-creator-core and write a small amount of Laravel code for models, routes, storage, and validation. If you are in a Blade or Livewire monolith that needs a fast survey capability and has no existing form builder, you can spike the wrapper as a reference implementation, then decide whether to adopt, fork, or rebuild. The evaluation recommends treating it as reference code rather than a dependency.