Getting started
Configuration
The default configuration runs every discovered Core analyzer. Narrow the scan only when your application has a documented reason to do so.
Analyzer discovery
The wildcard selects every analyzer under the configured analyzer paths. Additional packages, including LaraBeacon Pro, register their own namespace and directory through this extension point.
'analyzers' => ['*'],
'analyzer_paths' => [
'BaerSoftware\\LaraBeacon\\Analyzers' => LaraBeacon::analyzerPath(),
],Application paths
Core scans application code, routes, configuration, bootstrap behavior, migrations, and seeders. Add a custom path when product code lives outside Laravel’s conventional directories.
Do not add vendor, generated caches, minified bundles, or third-party source directories to the application scan.
Environment-specific checks
Set LARABEACON_SKIP_ENVIRONMENT_SPECIFIC=true when a local or isolated CI environment cannot represent production infrastructure. Run those checks separately against a production-like release candidate.
Baselines
A baseline records findings your team has reviewed. Generate it only after the initial report has been triaged.
php artisan larabeacon:baseline --ciThe command updates ignore_errors in config/larabeacon.php. Commit the change and review future baseline updates like code.
Optional Cloud reporting
Cloud transport remains off until an endpoint and credentials are configured and you invoke --report. Findings include paths, line numbers, and analyzer messages. Source snippets and exception stack traces are excluded by default and require separate opt-ins.