mightyiam/eslint-config-love - Open Source PR Review Scorecard

A TypeScript ESLint config that loves you

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

External PR Merge Rate: 44%

Response Time: -

First Timer Success: 50%

Frequently Asked Questions

Is mightyiam/eslint-config-love welcoming to first-time open-source contributors?

mightyiam/eslint-config-love has a recorded first-timer success rate of 50.0%. 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 mightyiam/eslint-config-love 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 54.8 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 54.8 places mightyiam/eslint-config-love in the B tier.

What is the external contributor pull request merge rate for mightyiam/eslint-config-love?

The external contributor pull request merge rate for mightyiam/eslint-config-love is 44.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in mightyiam/eslint-config-love?

mightyiam/eslint-config-love currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

mightyiam
mightyiam/eslint-config-loveB•Solid817
GitHub
Back to Explorer
mightyiam

mightyiam/eslint-config-love

817
InactiveB•Solid(55/100)Low Sample (<20 PRs)TypeScript

A TypeScript ESLint config that loves you

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.6/10
Patience Score
8.2/10
Nitpick Rate
25%

Collaborative maintainer environment in mightyiam/eslint-config-love. Reviews community pull requests with focus on project quality.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
44.4%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
2 core
Small core review team
Diagnostic Health HUD
44.4%
Merge Gauge
50.0%
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 mightyiam/eslint-config-love
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/mightyiam/eslint-config-love)](https://getmerged.abhishekco.de/mightyiam/eslint-config-love?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

Perhaps not all rules should be set to error. For example, unused variables. Why? Because they may disappear later on in the process of writing code. Another example is complexity-related rules. Perhaps they should be set to warn for the same reason. Eventually, the user is expected to disallow warnings before committing changes.

📅 Opened May 7, 2026💬 4 comments
Quality: 70/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript 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 mightyiam/eslint-config-love

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

Frequently Asked Questions - Contributing to mightyiam/eslint-config-love

01

Is mightyiam/eslint-config-love welcoming to first-time open-source contributors?

mightyiam/eslint-config-love has a recorded first-timer success rate of 50.0%. 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 ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 54.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 54.8 places mightyiam/eslint-config-love in the Solid tier.

04

What is the external contributor pull request merge rate for mightyiam/eslint-config-love?

The external pull request merge rate is 44.4%. 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 mightyiam/eslint-config-love?

Yes, mightyiam/eslint-config-love currently has 1 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 mightyiam/eslint-config-love 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.