New and resolved findings
Compare a report with the latest matching project and environment so regressions are separated from existing work.
Invitation-only early access
Keep the evidence from one release to the next.
LaraBeacon Cloud is the optional history and review layer for Core and Pro reports: protected projects, environments, category pass rates, new findings, resolved findings, and precise analyzer context.
New3
Resolved7
Category pass rates
Perf. 91%
Sec. 98%
Rel. 94%
Open findings
- Queue timeoutMajor
- Slow requestMajor
- Missing SRIMinor
Reliability / New in #48
Queue timeout alignment
The worker timeout is longer than the queue retry window. A job may be delivered again while its first execution is still active.
config/queue.php · lines 42–46 · optional context
'retry_after' => 90,
// worker: --timeout=120Report anatomy
The useful parts of an analysis, without a decorative dashboard.
The Cloud view follows the decisions developers actually make: what changed, where it happened, why it matters, and whether the same issue existed in the prior report.
Overall and category pass rates
Read performance, security, and reliability separately instead of compressing unlike risks into one confidence score.
Analyzer details and line context
Keep severity, documentation, paths, line numbers, and optional code snippets attached to the finding that produced them.
Projects, reports, and team access
Navigate prior reports, invite collaborators, and retain evidence according to the project’s selected plan.
Commit and pull-request context
Associate reports with a branch, revision, issue, or review so a release discussion links back to exact analyzer evidence.
Terminal and Cloud remain consistent
The local analyzer owns the result. Cloud presents the submitted report and does not replace local execution.
Data boundary
Submission is explicit. Source context is optional.
Installing Core does not connect a project to Cloud. A report is submitted only with --report and configured credentials; code snippets are removed by default.
Analysis runs in your application.
Core and Pro execute inside the Laravel project and build the report locally.
No background upload.
The Cloud client is invoked only by the report option and requires an endpoint plus access token.
Code snippets are off by default.
Project metadata and analyzer results can include file paths and line numbers. Source context needs a separate opt-in.
The payload is documented.
Teams can inspect the report contract before enabling transport and keep using local JSON output without Cloud.
Delivery order
Available now, with repository automation next.
Secure project ingestion · available
Hashed project credentials, payload validation, rate limits, retention controls, and a documented privacy boundary.
Report comparison · available
New and resolved analyzer results across the same project and environment.
Team access · available
Invitation-only accounts, ownership, administrator and member roles, and shared project history.
Repository integrations · planned
Focused GitHub report and review comments after the early-access reporting model is proven.
Early access