laravel/framework - Open Source PR Review Scorecard

Laravel is a web application framework with expressive, elegant syntax.

C-Rank Grade: A (Welcoming) - 67/100

External PR Merge Rate: 50%

Response Time: -

First Timer Success: 45%

Frequently Asked Questions

Is laravel/framework welcoming to first-time open-source contributors?

laravel/framework has a recorded first-timer success rate of 44.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in laravel/framework respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 67.1 C-Rank™ score (A Tier) represent?

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 67.1 places laravel/framework in the A tier.

What is the external contributor pull request merge rate for laravel/framework?

The external contributor pull request merge rate for laravel/framework is 49.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in laravel/framework?

laravel/framework currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

laravel
laravel/frameworkA•Welcoming35.0k
GitHub
Back to Explorer
laravel

laravel/framework

34,960
Active (30d)A•Welcoming(67/100)PHP

Laravel is a web application framework with expressive, elegant syntax.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.4/10
Patience Score
8.4/10
Nitpick Rate
45%

Highly welcoming maintainers in laravel/framework. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Follow maintainer feedback from recent PR reviews

Top PR Friction Pitfalls (Don'ts)

  • •Do not ignore unresolved maintainer review comments
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
49.7%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
44.6%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
97 core
Highly collaborative maintainer core
Diagnostic Health HUD
49.7%
Merge Gauge
44.6%
1st-Timer
Community Vibe33/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for laravel/framework
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/laravel/framework)](https://getmerged.abhishekco.de/laravel/framework?utm_source=github&utm_medium=badge)

Active Good First Issues (4)

View on GitHub

Laravel version: 13.24.0 PHP version: 8.5.9 Database driver & version: SQLite 3 in memory, through Testbench 11.1 I was counting queries on an ordinary index endpoint and ended up with 101 queries for 100 records with ?include=comments. The same listing built as Post::with('comments')->get() gives 2. Before I read anything into that I'd like to know whether the loading is meant to be the developer's job here. Where it comes from, as far as I can tell. ResolvesJsonApiElements:: compileResourceRelationships() calls $this->resource->loadMissing(...), and $this->resource in that method is always a single model, because both callers return early unless it is one. AnonymousResourceCollection::toAttributes() then maps resolveResourceData() over the collection item by item, so every item runs its own loadMissing against its own model. The nested level behaves differently, and that's why I'm asking rather than just eager loading and moving on. With 10 posts and ?include=comments.author I get 2

📅 Opened Aug 20, 2026💬 3 comments
Quality: 50/100Contribute

Laravel Version 13.11.2 PHP Version 8.5.4 Database Driver & Version No response Description On Windows 11, running laravel new fails during the post-autoload scripts when artisan install:features is executed. The command triggers an interactive prompt, which causes the Composer script to fail with exit code 255. > Illuminate\Foundation\ComposerScripts::postAutoloadDump > @php artisan package:discover --ansi INFO Discovering packages. inertiajs/inertia-laravel ................................................................................................................... DONE laravel/fortify ............................................................................................................................. DONE laravel/pail ................................................................................................................................ DONE laravel/pao ...............................................................................................

📅 Opened May 24, 2026💬 6 comments
Quality: 40/100Contribute

Laravel Version 13.11.1 PHP Version 8.4 Database Driver & Version N/A Description Based on the documentation for @stack I would expect to be able to define a @push basically anywhere and have it rendered into the stack. I have come across 2 scenarios where this does not appear to work. The first is very contrived, and not a realistic way the feature would be used, but could be indicative of the underlying problem. //welcome.blade.php @push('scripts') before stack @endpush @stack('scripts') @push('scripts') after stack @endpush In this example, the stack and push are defined in the same view file. Only "before stack" is rendered. There's really no need to make this scenario work because if you're in the same file you don't need to bother pushing to a stack, but including it to showcase the full failure scenario. The 2nd example is the specific issue I have run into, and what I hope we can make work. To replicate this issue we need 2 components and 1 view. I've used class

📅 Opened May 21, 2026💬 8 comments
Quality: 30/100Contribute

Laravel Version v13.2.0 PHP Version 8.3.30 Database Driver & Version mariadb Ver 15.1 on arm64 (Homebrew) Description When doing something along the lines of: $query ->where([ ['source_type', '=', Role::class], ['source_id', '=', $obj->guestRole->id], ]) ->orWhere([ ['source_type', '=', Group::class], ['source_id', '=', $obj->loggedOutGroup->id], ]); previously, it would generate a conditional with: (source_type=? AND source_id=?) OR (source_type=? AND source_id=?) After the upgrade to Laravel 13 it's now generating the following conditional (note the OR in the second block): (source_type=? AND source_id=?) OR (source_type=? OR source_id=?) While looking into this I discovered #53184 from 11.28 causing this issue. However, it says it was fixed in #53197 but I'm still seeing thi

📅 Opened Apr 3, 2026💬 4 comments
Quality: 45/100Contribute
Looking for more PHP beginner tasks?Explore PHP GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for laravel/framework

When evaluating whether to contribute to laravel/framework, 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/framework acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 49.7% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to laravel/framework

01

Is laravel/framework welcoming to first-time open-source contributors?

laravel/framework has a recorded first-timer success rate of 44.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 67.1 C-Rank™ score represent?

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 67.1 places laravel/framework in the Welcoming tier.

04

What is the external contributor pull request merge rate for laravel/framework?

The external pull request merge rate is 49.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in laravel/framework?

Yes, laravel/framework currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for laravel/framework 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.