keras-team/keras - Open Source PR Review Scorecard

Deep Learning for humans

C-Rank Grade: B (Solid) - 48/100

External PR Merge Rate: 64%

Response Time: 6d

First Timer Success: 47%

Frequently Asked Questions

Is keras-team/keras welcoming to first-time open-source contributors?

keras-team/keras has a recorded first-timer success rate of 47.3%. Repositories ranked B 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 keras-team/keras respond to incoming external pull requests in approximately 141.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 48.5 C-Rank™ score (B 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 48.5 places keras-team/keras in the B tier.

What is the external contributor pull request merge rate for keras-team/keras?

The external contributor pull request merge rate for keras-team/keras is 63.9%, based on public PR activity from non-core contributors.

Are there Good First Issues available in keras-team/keras?

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

keras-team
keras-team/kerasBSolid64.3k
GitHub
Back to Explorer
keras-team

keras-team/keras

64,270
BSolid(48/100)Python

Deep Learning for humans

Compare
Jump to:
Response Velocity
5 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
63.9%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
47.3%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
39 core
Highly collaborative maintainer core
Diagnostic Health HUD
63.9%
Merge Gauge
47.3%
1st-Timer
Community Vibe40/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

This repository currently has 2 open good first issue tickets available for newcomers.

View all good first issues directly on GitHub

Looking for more Python beginner tasks?Explore Python 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 keras-team/keras

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

Frequently Asked Questions - Contributing to keras-team/keras

01

Is keras-team/keras welcoming to first-time open-source contributors?

keras-team/keras has a recorded first-timer success rate of 47.3%. Repositories ranked Solid 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 ~5 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 48.5 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 48.5 places keras-team/keras in the Solid tier.

04

What is the external contributor pull request merge rate for keras-team/keras?

The external pull request merge rate is 63.9%. 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 keras-team/keras?

Yes, keras-team/keras currently has 2 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 keras-team/keras 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.