What does the 58.8 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 58.8 places Reference-LAPACK/lapack in the A tier.

Are there Good First Issues available in Reference-LAPACK/lapack?

Reference-LAPACK/lapack does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

Back to Explorer

Reference-LAPACK/lapack

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

Maintainers in Reference-LAPACK/lapack respond to incoming external pull requests in approximately 7.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

Q: What is the external contributor pull request merge rate for Reference-LAPACK/lapack?

The external contributor pull request merge rate for Reference-LAPACK/lapack is 54.5%, based on public PR activity from non-core contributors.

1,908

InactiveA•Welcoming(59/100)FOFortran

LAPACK development repository

GitHub

Compare••

Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score

9.1/10

Patience Score

9.0/10

Nitpick Rate

20%

Highly welcoming maintainers in Reference-LAPACK/lapack. Prompt code reviews with positive guidance for new contributors.

What Contributors Actually Say

Discussions in Reference-LAPACK/lapack focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

•1) Keep PR scope strictly aligned with the linked issue.
•2) Ensure local linters pass before opening a review.
•3) Maintain full test coverage for modified logic.

Top PR Submission Do's

•Add or update tests for changed behavior before requesting review
•Call out API, migration, or compatibility impact clearly
•Update docs or README when behavior changes

Top PR Friction Pitfalls (Don'ts)

•Do not leave requested test coverage unresolved
•Do not hide breaking changes in implementation details
•Do not ship user-facing changes without matching docs

Response Velocity

7 hours

Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency

54.5%

Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success

66.7%

Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers

16 core

Highly collaborative maintainer core

Diagnostic Health HUD

54.5%

Merge Gauge

66.7%

1st-Timer

Community Vibe66/100

Embed C-Rank Badge

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

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

90-Day C-Rank Trajectory

2 snapshots

Historical health & responsiveness evolution

52.1/100B

Sep 28

-7.9

Sep 24Range: 52.1 – 60.0 ptsSep 28

PR Acceptance & Review Speed Forecast

Precomputed via Live PR Events

Overall Merge Odds

54.5%

External PR acceptance

First-Timer Rate

66.7%

First PR success rate

Median Response (p50)

50% receive response in

Tail Latency (p90)

N/A

90% receive response in

Active Maintainers: 16

Optimal PR Submission Window

Maintainer review activity heatmap & prime window prediction

Wednesday - FridayConfidence: 52%

Peak Review Hour

14:00 UTC

Calculating local time...

Primary Window

12:00 - 16:00 UTC

Calculating local time...

Active Maintainers

9 Tracked

Detected: UTC

24-Hour Maintainer Activity Heatmap (UTC)

LowPeak

00:0006:0012:0018:0023:00

Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).

PR Size vs Review Speed

Best Pull Request Size for Reference-LAPACK/lapack

Sweet Spot: < 150 lines

Small (<150 LOC)Recommended

5havg review

68% Merge Approval

Medium (150–500 LOC)Normal

11havg review

52% Merge Approval

Large (>500 LOC)Slow

1.4davg review

25% Merge Approval

Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (68% approval). Large PRs (>500 lines) take ~34 hours (25% approval). Keep your diff compact for rapid review.

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for Reference-LAPACK/lapack.

View all good first issues directly on GitHub

Looking for more Fortran beginner tasks?Explore Fortran 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 Reference-LAPACK/lapack

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

Frequently Asked Questions - Contributing to Reference-LAPACK/lapack

Is Reference-LAPACK/lapack welcoming to first-time open-source contributors?

Reference-LAPACK/lapack has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming 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?

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

What does the 58.8 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 58.8 places Reference-LAPACK/lapack in the Welcoming tier.

What is the external contributor pull request merge rate for Reference-LAPACK/lapack?

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

Are there beginner Good First Issues open in Reference-LAPACK/lapack?

Reference-LAPACK/lapack does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for Reference-LAPACK/lapack 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.