LaraBeacon

Workflows

Cloud reporting

Core runs without an account or network connection. Cloud transport occurs only when credentials are configured and the command is invoked with --report.

Invitation-only early access

Cloud accounts and project licences are currently granted manually. There is no public registration or active checkout. Existing users can open Cloud; new teams can request an invitation.

Enable a report endpoint

Create a licensed project in Cloud, then copy the username and one-time token into protected environment variables. Never commit the token. If it is lost, rotate it in the project view.

LARABEACON_CLOUD_ENDPOINT=https://larabeacon.com/api/
LARABEACON_CLOUD_USERNAME=lbp_project-username
LARABEACON_CLOUD_API_TOKEN=replace-with-a-secret

The client accepts only an absolute HTTPS endpoint and refuses redirects to unencrypted HTTP targets.

Then submit a run deliberately:

php artisan larabeacon --ci --report --hash="$GIT_COMMIT"

The API accepts at most 900 KB per report, authenticates each request against the assigned project licence, and queues normalization. The returned URL remains protected by the team login.

Default payload

A report contains enough information to identify and compare a run:

  • application name, environment, configured URL, Composer project name, repository identifier, commit, and trigger;
  • analyzer title, class, category, severity, time-to-fix estimate, status, error message, documentation URL, and reporting state;
  • finding paths, line numbers, and analyzer details;
  • passed, failed, skipped, errored, and reportable totals by category.

Paths and analyzer messages can themselves contain sensitive project information. Inspect your application’s findings before enabling an upload.

Sensitive diagnostics are excluded by default

Cloud reports omit source snippets and exception stack traces unless each category is explicitly enabled.

# Default: false
LARABEACON_CLOUD_INCLUDE_CODE_SNIPPETS=false
LARABEACON_CLOUD_INCLUDE_EXCEPTION_STACK_TRACES=false
Opt in narrowly

Source snippets may include credentials, personal data, or proprietary logic. Exception stack traces may reveal internal paths and call structure. Enable either setting only after reviewing your data policy and Cloud access controls.

Repository context

Set LARABEACON_GITHUB_REPO=owner/repository when a report should be associated with a repository. Use --issue, --review, and --hash only together with --report; without a report submission they do not contact a service.

History and retention

Reports are numbered within a project. After processing, Cloud compares a run with the latest completed report for the same project and environment. It marks newly open findings and shows findings that have been resolved since that prior run.

The raw request body is discarded after processing. Normalized report history is retained for 60 days on Solo, 90 days on Team, and 180 days on Enterprise, then removed by the daily retention job.

Teams and project licences

A Team or Enterprise workspace can invite any number of members. Member seats do not consume licences. Each independently developed Laravel codebase consumes one project licence; its development, staging, and production environments remain part of that same project.

Archiving revokes project API tokens but deliberately keeps the licence assignment. This prevents silent reuse for a different customer application. Additional project purchases add explicit slots to the existing team licence.

Disable transport

Remove the Cloud endpoint and credentials and omit --report. Local terminal analysis, CI exit codes, and baselines continue to work unchanged.

RelatedOpen LaraBeacon Cloud