Laravel Pulse is a real-time application performance monitoring tool and dashboard for your Laravel application.
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 64%
Response Time: 7d
First Timer Success: 100%
laravel/pulse has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in laravel/pulse respond to incoming external pull requests in approximately 176.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 46.3 places laravel/pulse in the B tier.
The external contributor pull request merge rate for laravel/pulse is 64.3%, based on public PR activity from non-core contributors.
laravel/pulse 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/pulse. 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/pulse?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~115 hours (80% approval). Large PRs (>500 lines) take ~849 hours (29% approval). Keep your diff compact for rapid review.
Pulse Version v1.7.3 Laravel Version 13.4.0 PHP Version 8.4.14 Livewire Version 4.2 Database Driver & Version 12.0.2-MariaDB-ubu2404 Description Laravel Pulse v1.7.2 and also v1.7.3 is still not compatible with Laravel 13. Issue #503 was closed by author but the underlying incompatibility between Pulse and Laravel 13's new default still exists and will affect every new installation. # Error - Internal Server Error The script tried to call a method on an incomplete object. Please ensure that the class definition "Illuminate\Support\Collection" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide an autoloader to load the class definition PHP 8.4.14 Laravel 13.4.0 localhost ## Stack Trace 0 - vendor/laravel/pulse/src/Livewire/Queues.php:35 1 - vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:36 2 - vendor/laravel/framework/src/Illuminate/Container/Util.php:43 3 - vendor/laravel/framework/src/Illuminate/Container/BoundMet
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/pulse, 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/pulse acknowledge new external contributions in approximately 7 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.3% were successfully merged into the primary branch.
laravel/pulse has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 days+. 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 46.3 places laravel/pulse in the Solid tier.
The external pull request merge rate is 64.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
laravel/pulse 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/pulse 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.