laravel maintained by stackradar
StackRadar for Laravel
See which Composer packages are deployed in each environment. The package reports from your web and queue runtimes every ten minutes, using normal application activity. No cron or daemon required.
Supports Laravel 12+. Requires PHP 8.2+ and the PHP version required by your Laravel release.
Install with your agent
Paste this prompt into your coding agent from your application repository:
Install StackRadar runtime reporting in this Laravel app:
https://github.com/stackradar/stackradar-laravel
Ask which deployed environments and StackRadar Project to use.
Follow this app's deployment and secrets workflow, keeping ingest
keys out of chat and tool output. Have me enter secrets directly
where needed.
Make the changes, run relevant checks, and verify reporting from
each selected environment. State anything still awaiting deployment
or verification.
Manual installation
composer require stackradar/laravel
Configure
Laravel discovers the package automatically. Set your Project's Ingest Key in your deployment secrets or environment settings:
STACKRADAR_INGEST_KEY=your-ingest-key
The environment defaults to APP_ENV. The service defaults to a slug of APP_NAME: My Customer API becomes my-customer-api. Override these with STACKRADAR_ENVIRONMENT and STACKRADAR_SERVICE. Use distinct service names for apps sharing a Project.
Without a key, nothing is reported. Reporting is disabled during Laravel tests. Set STACKRADAR_RELEASE to identify deployments. Runtime reporting must be enabled for your organization in StackRadar.
For other settings:
php artisan vendor:publish --tag=stackradar-config
Use STACKRADAR_CACHE_STORE to select a persistent cache with atomic locks; the default is file. Set STACKRADAR_DEBUG=true for diagnostics. Invalid keys and rejected inventories warn once without enabling debug.
On Vapor or read-only containers, set STACKRADAR_CACHE_STORE to redis or dynamodb.
Check the connection
php artisan stackradar:report
This sends one CLI report and prints any failure reason. Web and queue reporting continues automatically. Idle apps won't send heartbeats, and long-lived workers need restarting on deployment.
Development
composer install
composer check
Tests use Laravel Testbench and fake transports; they don't call StackRadar.