LaraBeacon

Workflows

Continuous integration

CI mode runs the checks designed to be deterministic in an isolated pipeline and returns a non-zero exit status when reportable findings fail.

Basic release gate

php artisan larabeacon --ci --details

Run the command after dependencies and application configuration are available. Keep it next to tests, static analysis, and the production asset build.

GitHub Actions example

- name: Run LaraBeacon
  env:
    APP_ENV: testing
    APP_KEY: base64:your-ci-key
  run: php artisan larabeacon --ci --details
Do not commit real secrets

Use the secret store of your CI provider for credentials. The example key is a placeholder and must not be reused.

Runtime stage

HTTP headers, production caches, queue workers, Redis, filesystem capacity, Telescope evidence, and similar signals need a representative environment. Run them against a release candidate before the final traffic switch, not against a synthetic CI container that cannot satisfy their assumptions.

Baseline policy

  • Review every new finding before adding it to a baseline.
  • Keep baseline changes in the same pull request as the responsible code or architecture decision.
  • Prefer narrow analyzer exclusions over disabling an entire category.
  • Regenerate the baseline periodically so deleted code does not leave stale entries behind.