Supercharge your Laravel application's performance.
C-Rank Grade: B (Solid) - 47/100
External PR Merge Rate: 47%
Response Time: 7h
First Timer Success: 44%
laravel/octane has a recorded first-timer success rate of 44.4%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in laravel/octane respond to incoming external pull requests in approximately 6.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 47.0 places laravel/octane in the B tier.
The external contributor pull request merge rate for laravel/octane is 47.2%, based on public PR activity from non-core contributors.
laravel/octane does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in laravel/octane. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/laravel/octane?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (59% approval). Large PRs (>500 lines) take ~33 hours (21% approval). Keep your diff compact for rapid review.
Octane Version 2.9 Laravel Version 12 PHP Version 8.4 What server type are you using? FrankenPHP Server Version 1.12 Database Driver & Version No response Description The current Caddy configuration template for FrankenPHP utilizes a broad try_files directive: try_files {path} frankenphp-worker.php This logic causes all requests for non-existent static files (e.g., versioned assets like app-v123.js after a deployment) to be forwarded to the PHP worker. In high-traffic environments, a surge of requests for missing assets triggers unnecessary PHP process execution, leading to worker saturation, increased CPU/Memory overhead, and potential system failure. Technical Impact Performance: High overhead for 404 responses that should be handled at the web-server level. Stability: Potential DoS condition when static asset paths are brute-forced or when client-side caches request deprecated versioned files. Resource Allocation: PHP workers are occupied by I/O-bound requests for missing files ins
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to laravel/octane, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of laravel/octane acknowledge new external contributions in approximately 6 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 47.2% were successfully merged into the primary branch.
laravel/octane has a recorded first-timer success rate of 44.4%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 47.0 places laravel/octane in the Solid tier.
The external pull request merge rate is 47.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
laravel/octane does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for laravel/octane are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.