- Is kitlabs/kit-soar-bundle a Laravel package?
- No. Despite the Laravel SOAR branding, the repository is a Symfony bundle with a Bundle subclass, DI extension, and compiler passes. Laravel's container cannot register it, and there is no service provider, facade, or publishable config/kit_soar.php. Treat it as a reference implementation rather than a Composer dependency.
- Does kitlabs/kit-soar-bundle support Laravel 10 or Laravel 11?
- It does not target Laravel at all; it is built as a Symfony bundle. There are no Laravel version constraints, auto-discovered service providers, or framework integration points. You would need to write your own adapter if you wanted to reuse any of its invocation logic.
- How do I install kitlabs/kit-soar-bundle in a Laravel application?
- Composer installation will not wire it into Laravel because it is not a Laravel package. To use the underlying idea, port the thin invocation and config logic behind your own Laravel service provider and runner service. You would also need to install, pin, and checksum the external soar binary in every environment.
- What does kitlabs/kit-soar-bundle actually do?
- The artifact is a thin process wrapper that shells out to XiaoMi's soar Go binary, pipes SQL into it, and parses human-oriented CLI text output. It is roughly 200 lines of glue around an external binary, not a full SOAR orchestration engine. The binary is the real asset; the wrapper is negligible.
- Do I need the Xiaomi soar binary to use this package?
- Yes. The soar binary is not installable via Composer, so you must deliver it as a pinned, checksummed artifact in every environment the feature touches. For EXPLAIN-based checks, the target MySQL instance must also accept connections with usable credentials. Those are operational prerequisites, not PHP problems.
- Can kitlabs/kit-soar-bundle run SOAR playbooks, approvals, and event triggers?
- The marketing description claims playbook definitions, event-driven triggers, pluggable actions, and execution logging. The actual repository does not implement Laravel SOAR orchestration; it wraps the soar SQL optimizer CLI. Developers should verify claims against the code and avoid assuming the advertised workflow features exist.
- Is kitlabs/kit-soar-bundle maintained and safe for production?
- Adoption signals are effectively zero: one star, zero dependents, and a bus factor of one. Upstream XiaoMi soar has been dormant for years, so you would inherit unmaintained SQL parsing and MySQL-version assumptions. SQL text and EXPLAIN DSNs also cross into a subprocess, which needs explicit security sign-off before production use.
- What are alternatives to kitlabs/kit-soar-bundle for SQL linting in Laravel?
- If you want the capability, wrap the soar binary directly in a small, owned Artisan command instead of adopting this package. For the linting subset, evaluate PHP-native parsers such as greenlion/php-sql-parser or phpmyadmin/sql-parser, which remove the external binary entirely. For broader SOAR workflows, build owned Laravel events, queues, and services rather than relying on this bundle.
- How should I test output parsing if I wrap the soar binary myself?
- The bundle provides no test coverage on your side, and parsing human-oriented CLI text is fragile across binary upgrades. Add fixture-based tests around the exact soar output you depend on, pin the binary version, and fail loudly on parse errors. Otherwise a binary bump can silently break parsing and produce false clean passes.
- Does kitlabs/kit-soar-bundle support MySQL 8 CTEs and window functions?
- That depends entirely on the pinned soar binary, not on the PHP wrapper. Since upstream soar is dormant, verify MySQL 8.x syntax support, including CTEs and window functions, against your actual workload before committing. Run a spike with representative queries and a measurable success criterion before treating it as production-ready.