Weave Code
Goat Query Laravel Package
makinacorpus/goat-query
Goat Query is a Laravel package for composing database queries with a fluent, reusable API. It helps structure filters, joins, and conditions cleanly, making complex Eloquent queries easier to build, maintain, and test.
Goat SQL query builder built over a PHP to SQL and SQL to PHP type converter
Frequently asked questions about Goat Query
- Does Goat Query integrate with Laravel Eloquent and the query builder?
- Goat Query does not appear to ship a Laravel service provider, facade, or Eloquent integration. It is a standalone SQL builder that overlaps with Laravel's Query Builder and Eloquent rather than complementing them. In Laravel you would need to wrap it manually and manage connections, transactions, and events yourself.
- How do I install makinacorpus/goat-query in a Laravel application?
- Install it with composer require makinacorpus/goat-query, but expect manual wiring rather than Laravel auto-discovery. The assessment found no service provider or facade, so register any bindings yourself or place it behind an internal adapter. Check the package's composer.json for PHP constraints and complete a GPL-2.0 license review before installing it in product code.
- What Laravel and PHP versions does Goat Query support?
- The provided context does not document supported Laravel or PHP versions, and there is no visible CI matrix confirming currency. With only 2 stars and 0 dependents, there is no downstream evidence that recent PHP or Laravel releases are tested. Inspect composer.json, tags, and CI configuration, and assume nothing until you run it against your exact support policy.
- Is Goat Query safe to use in production Laravel applications?
- Treat it as high risk for production Laravel use. The GPL-2.0 license is a legal gate, the package has minimal third-party validation, and it bypasses Laravel's DB connection, transaction, and event layers unless wrapped. Verify parameter binding and run a timeboxed spike before committing engineering time.
- Can I use Goat Query only for PHP-to-SQL type conversion without the query builder?
- The PHP-to-SQL type converter is the most differentiated part, but the package does not document a supported converter-only path in the provided context. Inspect its namespaces and autoload map to see whether the converter can be used without the builder. If you adopt it, isolate the converter behind your own TypeMapperInterface and write conformance tests for your target databases.
- What license does Goat Query use, and can I use it in commercial SaaS?
- Goat Query is GPL-2.0, which is copyleft and a hard constraint for proprietary or SaaS codebases. Do not link it into closed-source product code without legal review. Relicensing to MIT or Apache is not confirmed in the context, so ask Makina Corpus before spending engineering time.
- How does Goat Query prevent SQL injection and handle parameter binding?
- The context does not confirm how Goat Query parameterizes values, and a builder is only safe if it emits bound parameters rather than interpolated literals. The PHP-to-SQL type converter must be audited for placeholders, especially around dates, decimals, booleans, JSON, and binary types. No fuzz or security test suite is mentioned, so add your own injection tests before use.
- Which database engines does Goat Query support and test?
- The assessment warns that cross-engine type conversion is leaky across MySQL, PostgreSQL, SQLite, and SQL Server, but no verified test matrix is provided. There is no visible CI evidence or downstream smoke testing for specific PDO drivers. Confirm supported engines and test dates, decimals, booleans, JSON, and transactions on each target database.
- Is Goat Query actively maintained or a good alternative to Laravel's query builder?
- No, it is not a good primary alternative to Laravel's Query Builder or Eloquent in a modern Laravel app. With 2 stars, 0 dependents, and no visible service-provider integration, there is little evidence of active maintenance or adoption. It may fit a non-Laravel PDO codebase or a narrow type-conversion utility, subject to the license gate.
- How should I isolate Goat Query in my codebase or migrate away from it?
- Do not let Goat Query types leak across the codebase. Introduce thin internal interfaces such as QueryBuilderInterface and TypeMapperInterface, implement them with Goat behind that boundary, and keep call sites framework-native. Add conformance tests for the target DB engines so you can swap the implementation or migrate back to Laravel's builder with limited blast radius.
Weaver
How can I help you explore Laravel packages today?