- What is Grafite Mission Control used for in Laravel?
- Mission Control is a Grafite package that provides a central dashboard for监控 and managing a Laravel application, giving developers one place to review key resources and controls. It is a Composer-installable, MIT-licensed package, with framework bindings expected in a companion Laravel adapter. The exact entities it persists and the user-facing screens it exposes are not documented in the repo signals reviewed, so confirm scope with a static read of the source before relying on specific features.
- Does grafite/mission-control support Laravel 10, 11 and 12?
- This is not confirmed. The repo signals reviewed do not state which Laravel versions are supported, and with zero stars and zero dependents there is no downstream evidence of it running on Laravel 10, 11 or 12. Check the companion adapter's composer.json illuminate/* constraints and the core's PHP constraint before assuming compatibility. A sandbox install on your target Laravel version is the fastest way to verify.
- How do I install grafite/mission-control with Composer?
- On paper the path is to require the core plus its Laravel adapter, publish config and migrations, run migrations, and register the service provider or rely on auto-discovery if it is wired. In practice a fork-first approach is safer: mirror the repo, pin dependencies, run any test suite, then install from your own VCS. Budget for the fork as the default outcome rather than the fallback.
- Is grafite/mission-control still maintained?
- The assessment flags high abandonment risk: a single-vendor package from a small studio with a largely dormant ecosystem, a bus factor of one, zero stars and zero dependents. Check the last commit date and last release tag before committing, because that alone may rule it out. With no dependents there is no downstream pressure to patch, so any vulnerability becomes yours to find and fix.
- Does Mission Control work as a standalone PHP package or does it need a Laravel adapter?
- It is positioned as a PHP-agnostic core, which implies domain logic lives here and framework bindings live in a companion Laravel adapter. That means the value you would actually consume likely sits in the adapter, not in this repository. Evaluate the core and the adapter as a single two-package unit before making an adoption decision.
- What PHP version does grafite/mission-control require?
- The PHP version constraint is in composer.json and was not confirmed in the signals reviewed. Be aware that a PHP-agnostic core written for PHP 7.x will likely hit typed-property, return-type and deprecation issues on PHP 8.2 and above. Verify that the declared constraint overlaps your runtime before writing any application code against it.
- Is it safe to use grafite/mission-control in production?
- Not without a time-boxed spike. Key unknowns include whether the service provider touches APIs removed in Laravel 10, 11 or 12, whether it registers routes, middleware, scheduled tasks or outbound callbacks, and what its transitive dependencies are. Fork the package, pin dependencies, run tests in a sandbox, and confirm both framework and data compatibility. Also plan an exit migration, because adoption means you own the schema.
- Are there alternatives to Grafite Mission Control for Laravel monitoring?
- The assessment does not name specific alternatives; it recommends comparing against maintained Laravel monitoring and dashboard packages that declare support for your Laravel and PHP versions. Apply the same criteria: active releases, CI, dependents and clear adapter constraints. Laravel Telescope, Horizon and Pulse are commonly used for monitoring in Laravel estates, though exact overlap with Mission Control's feature set should be verified.
- How do I test or evaluate grafite/mission-control before adopting it?
- Run it as a time-boxed spike rather than a project. Day one is a static read of composer.json, the changelog, the test directory and the last-commit date; day two is a sandbox install into a throwaway Laravel app of your target version. Confirm whether config and migrations are publishable, whether auto-discovery is wired, and whether any outbound HTTP calls, phone-home behavior or license key requirements exist.
- Does grafite/mission-control publish config and migrations, and does it use package auto-discovery?
- This is not confirmed by the repo signals. Publishing config and migrations and wiring auto-discovery are standard Laravel package conventions, but the assessment lists both as open unknowns to verify. Look for a service provider with publishes() calls and an extra.laravel block in composer.json, then confirm the behavior during a sandbox install.