Weave Code
Ajaxgrid Laravel Package
evolutto/ajaxgrid
TaoSistemasAjaxGridBundle (evolutto/ajaxgrid) is an AJAX grid bundle for Symfony 3 that adds AJAX-driven data grid functionality to Symfony applications. The README is minimal, so inspect the source and confirm Symfony 3 compatibility before adopting it.
Symfony AjaxGridBundle
Frequently asked questions about Ajaxgrid
- Can I install evolutto/ajaxgrid in a Laravel application?
- No. The package is a Symfony 3 bundle, not a framework-agnostic PHP library: it depends on Symfony's Bundle base class, the DI container, and typically Twig for rendering, none of which Laravel provides or registers. Laravel has no bundle mechanism, and its container, router, and Blade templating use different contracts. Making it work would mean vendoring the source, rewriting the bundle class as a service provider, and porting Twig templates to Blade, at which point you have kept only the source code, not the integration.
- What does TaoSistemasAjaxGridBundle actually do?
- The README is two sentences long and only says "ajax grid for symfony3", so the feature set is undocumented. An AJAX grid normally implies server-side pagination, filtering, and sorting, possibly inline editing or export, but none of that is confirmed here. You would have to read the source to determine whether it ships a JavaScript layer, how the query is constructed, and what configuration options exist. Treat any capability claims as unverified until you audit the code.
- Which Symfony and PHP versions does this bundle support?
- It targets Symfony 3, which reached end of life in November 2021. Symfony 3 era code typically supports PHP 5.5 through 7.x and is very unlikely to parse or run cleanly on PHP 8.2. Check the composer.json constraints for symfony/* and php before considering anything, and expect a hard conflict with any modern stack.
- Is evolutto/ajaxgrid compatible with Laravel 10 or Laravel 11?
- Almost certainly not. Laravel 10 and 11 require PHP 8.1+ and their own HTTP kernel, container, and view layer, while this bundle was written for Symfony 3 and PHP 7-era APIs. The only worthwhile compatibility check is negative: confirm the composer constraints and see whether installation even resolves. Do not plan engineering work around a port, because a reimplementation is cheaper than adapting a dead Symfony 3 bundle.
- What license is this package under, and can I use it in a commercial product?
- It is GPL-2.0, a strong copyleft license. Linking GPL code into a proprietary Laravel application and distributing that application is very likely to trigger source-disclosure obligations for the whole combined work. For most commercial products this alone is disqualifying, regardless of technical merit. Run it past legal before any code enters your repository.
- Is evolutto/ajaxgrid actively maintained?
- There are no signals of maintenance: the README is the only documentation, and the package has zero stars and zero dependents, so there is no production usage or community to learn from. Provenance is also murky, since the evolutto vendor namespace does not match the h00dstoker repository owner or the TaoSistemas repo name, suggesting a fork or rename with unclear lineage. That combination is a supply-chain and due-diligence red flag.
- Does the package have documentation, tests, or usage examples?
- No. The maturity level is effectively "readme", and the README itself is two sentences, so there is no installation guide, no configuration reference, no usage example, and no test suite. Without a test suite you cannot verify behaviour on upgrade, and without examples you cannot validate your integration. Everything would have to be reverse-engineered from the source.
- Is it safe to use? What about SQL injection and CSRF?
- That cannot be ruled out without a full source audit. An AJAX grid implies server-side query construction, filtering, and sorting, and with no tests or documented input handling, string-concatenated filters and missing CSRF protection are real possibilities. Treat any adoption as requiring a security review of the query builder and every request endpoint, including the JavaScript layer. Given the framework mismatch, that effort is usually not worth spending.
- How do I install it with Composer, and what registration is required?
- Composer would install the package into vendor/, but a Symfony bundle must then be registered in the kernel (AppKernel on Symfony 3), which Laravel has no equivalent for. In a Laravel app there is nothing to register and nothing to boot, so installation alone delivers no working functionality. Expect dependency resolution to fail anyway against modern PHP and symfony/* constraints.
- What are the Laravel alternatives for a server-side AJAX data grid?
- The Laravel-native options are mature, MIT-licensed, and PHP 8 compatible: yajra/laravel-datatables for DataTables-backed server-side grids, Livewire or Filament's table component for reactive grids with less JavaScript, and Inertia with a client-side table library. For lightweight hand-rolled grids, combine spatie/laravel-query-builder with kyslik/column-sortable for filtering and sorting. Any of these gives you documentation, an active maintainer base, and no copyleft obligation, which is the opposite of this package on every dimension.
Weaver
How can I help you explore Laravel packages today?