Backend controllers and scaffolding for Laravel authentication.
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 83%
Response Time: 2d
First Timer Success: 100%
laravel/fortify has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in laravel/fortify respond to incoming external pull requests in approximately 51.7 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 55.6 places laravel/fortify in the A tier.
The external contributor pull request merge rate for laravel/fortify is 83.3%, based on public PR activity from non-core contributors.
laravel/fortify does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Active PHP repository in laravel/fortify with ongoing community development and issue triage.
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/fortify?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 Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~34 hours (96% approval). Large PRs (>500 lines) take ~248 hours (38% approval). Keep your diff compact for rapid review.
Fortify Version v1.37.2 (the three files involved are byte identical on v1.37.3, the current release) Laravel Version 13.19.0 PHP Version 8.4.22 Database Driver & Version MariaDB 11.8.8. Not database dependent. Description With Features::twoFactorAuthentication(['confirm' => true]), clicking "Enable 2FA" a second time within the same page session destroys the pending, unconfirmed two_factor_secret instead of doing nothing. The setup modal then reopens and requests GET /user/two-factor-secret-key, which returns 404 because the secret it is asking for was deleted moments earlier by that same click. The result is a dead end: no QR code, no setup key, and nothing in the UI suggesting the only recovery (a full page reload). This is an interaction between two individually reasonable behaviours introduced 19 months apart: #518 (merged 2024-01-31) made EnableTwoFactorAuthentication a no-op when a secret already exists and force is false. #604 (merged 2025-08-29) added InteractsWithTwoFactorSt
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/fortify, 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/fortify acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.3% were successfully merged into the primary branch.
laravel/fortify has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 55.6 places laravel/fortify in the Welcoming tier.
The external pull request merge rate is 83.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
laravel/fortify 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/fortify 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.