- How do I install zeeshantariq/filament-sqlgen in a Laravel app?
- It is installed via Composer and then configured for your Filament panel, including a Gemini API key. The overview mentions Composer installation and Filament panel registration, but the exact commands and config keys are not included in the provided context, so check the repository README. Test the setup in a sandbox before connecting it to any real database.
- Which Laravel, PHP, and Filament versions does filament-sqlgen support?
- The provided context does not document a compatibility matrix, and the assessment says compatibility is unproven. The TPM notes recommend pinning exact versions and testing against your target Filament, Laravel, and PHP matrix, including whether Filament v2 or v3 is required. Treat version support as unconfirmed until you verify it in a short spike.
- Does filament-sqlgen execute the generated SQL or only display it?
- The overview says it converts natural language into SQL and shows results in real time, but it does not clearly state whether generated SQL is executed automatically or only displayed. The TPM assessment flags this as a key question and a high-risk area. Confirm the behavior in the source code before using it against any database.
- Can I restrict filament-sqlgen to a read-only database user and a query allowlist?
- The package overview does not document built-in read-only enforcement, query allowlisting, row limits, or approval workflows. The TPM assessment recommends isolating it behind a read-only replica, query allowlists, and human approval. Assume you need to add those guardrails yourself or fork and harden the package.
- Is filament-sqlgen safe for production Laravel admin panels?
- The TPM assessment rates it high risk and best viewed as a prototype accelerator, not a production component. Risks include unsafe generated SQL, prompt injection, schema or data leakage to Gemini, and execution against a privileged database user. Production use would require security review, sandboxing, audit logging, permission checks, and likely an internal fork.
- How is the Gemini API key configured for filament-sqlgen?
- Integration is described as Composer-based with configuration for a Gemini API key and Filament panel registration. The exact environment variable names, config file paths, and panel registration syntax are not documented in the provided excerpt. Check the repository README and source code before deploying it to a shared environment.
- What schema and data does filament-sqlgen send to Gemini?
- The provided context does not specify how prompts are constructed or what schema, query context, or sample data is sent to Gemini. Because data leakage is a flagged risk, review the source code and run a security and legal review before sending real schema or production data. Use synthetic or anonymized data in any pilot.
- Are there tests, releases, a license, or community support for filament-sqlgen?
- The assessment notes zero stars, zero dependents, no community validation, and no evidence of test coverage. License, release cadence, and roadmap are unknown until reviewed. Assume the package may be abandoned or break on Filament upgrades and budget for an internal fork.
- What alternatives exist to filament-sqlgen for natural-language-to-SQL in Laravel?
- The provided context does not name specific alternatives; it recommends deciding between build, fork, and buy after a time-boxed pilot. You could evaluate other Laravel or Filament AI query tools, or build a hardened internal feature using a database and AI provider you control. Swapping the Gemini dependency may only be practical if you fork or modify the package.
- How should I test or pilot filament-sqlgen before adopting it?
- Run a sandbox branch with a read-only replica, synthetic or anonymized data, and a feature flag. Measure output accuracy, latency, and Gemini cost against a small set of real analyst questions. Only then decide whether to fork and harden it internally rather than depending on upstream.