- What does the matriphe/larinfo package do?
- Larinfo is a Laravel package that adds a diagnostic endpoint displaying application and server details, including IP address, operating system, Laravel and PHP versions, environment, database information, and installed packages. It lets developers inspect configuration and runtime information without installing separate debugging tools. It is most useful during development or on protected staging environments.
- How do I install matriphe/larinfo in Laravel?
- Install it with Composer using the package name, for example composer require matriphe/larinfo. After installation, check the package README to confirm whether the service provider is auto-discovered or must be registered manually, and whether any config file needs to be published. Then load the diagnostic route the package registers in your application.
- Which Laravel versions does Larinfo support?
- The 4.3.0 release is documented as supporting Laravel 12. The release note does not confirm whether Laravel 10 and 11 remain supported, so treat the exact illuminate/support constraint in composer.json as the source of truth. If you are on an older LTS, verify the constraint before upgrading.
- Does Larinfo work with Laravel 12?
- Yes, release 4.3.0 explicitly adds Laravel 12 support. However, the release note does not state whether Laravel 12 is the only supported target or an addition to the existing support matrix, and no CI test matrix is mentioned. Confirm the composer.json constraints and test the endpoint in your app before relying on it in production.
- What PHP version does Larinfo require?
- Laravel 12 itself requires PHP 8.2 or later, so running Larinfo 4.3.0 on Laravel 12 implies PHP 8.2 or newer. The package's own php constraint is not visible from the release note, so read composer.json for the exact minimum. If you are on an older Laravel version, the package may allow a lower PHP version.
- Is it safe to leave Larinfo enabled in production?
- Larinfo exposes server and application details such as OS, PHP and Laravel versions, environment name, database information, and installed packages. That information is useful to attackers fingerprinting your stack, so the endpoint should not be publicly reachable in production. Restrict it with authentication middleware, an IP allowlist, or by disabling the route outside local and staging environments.
- How do I restrict access to the Larinfo endpoint?
- Wrap the package route with Laravel middleware such as auth or a custom gate, or conditionally register the route only in local and staging environments. If the package publishes a config file, check whether it offers an enable flag or middleware option. Otherwise, override the route in your application's route configuration or apply middleware at the route group level.
- How do I test the Larinfo endpoint in my Laravel application?
- Use Laravel's HTTP testing helpers to call the route the package registers and assert the expected status and response content. You may need to authenticate first if you have protected the endpoint with middleware. Because the exact route path and name are package-specific, confirm them in the package source or README before writing the test.
- What information does Larinfo display?
- According to the package overview, it shows IP address, operating system details, Laravel and PHP versions, application environment, database information, and installed packages. This is the kind of data developers usually gather manually with phpinfo, artisan about, or server commands. The exact layout and fields may vary by package version.
- What are alternatives to Larinfo for inspecting Laravel configuration?
- Laravel's built-in php artisan about command, along with Debugbar or Telescope, covers much of the same ground for local development. For structured health checks, packages like spatie/laravel-health provide endpoints with pass and fail results. Larinfo is lighter weight and focused on displaying environment and version details rather than profiling requests.