infeng/react-viewer - Open Source PR Review Scorecard

react image viewer, supports rotation, scale, zoom and so on

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

External PR Merge Rate: 88%

Response Time: <1h

First Timer Success: 100%

Frequently Asked Questions

Is infeng/react-viewer welcoming to first-time open-source contributors?

infeng/react-viewer has a recorded first-timer success rate of 100.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 infeng/react-viewer respond to incoming external pull requests in approximately 0.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 59.7 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 59.7 places infeng/react-viewer in the B tier.

What is the external contributor pull request merge rate for infeng/react-viewer?

The external contributor pull request merge rate for infeng/react-viewer is 87.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in infeng/react-viewer?

infeng/react-viewer does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

infeng
infeng/react-viewerB•Solid768
GitHub
Back to Explorer
infeng

infeng/react-viewer

768
InactiveB•Solid(60/100)Low Sample (<20 PRs)Capped at B (Bus Factor: 0)TypeScript

react image viewer, supports rotation, scale, zoom and so on

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 infeng/react-viewer. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in infeng/react-viewer 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

  • •Update docs or README when behavior changes
  • •Link the issue and include reproduction context in the PR
  • •Add or update tests for changed behavior before requesting review

Top PR Friction Pitfalls (Don'ts)

  • •Do not ship user-facing changes without matching docs
  • •Do not open context-free PRs
  • •Do not leave requested test coverage unresolved
Response Velocity
<1 hour
⚡ Fast reviewer response

Average Response Latency

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

Merge Efficiency
87.5%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
87.5%
Merge Gauge
100.0%
1st-Timer
Community Vibe94/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for infeng/react-viewer.

View all good first issues directly on GitHub

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 infeng/react-viewer

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

Frequently Asked Questions - Contributing to infeng/react-viewer

01

Is infeng/react-viewer welcoming to first-time open-source contributors?

infeng/react-viewer has a recorded first-timer success rate of 100.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 ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 59.7 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 59.7 places infeng/react-viewer in the Solid tier.

04

What is the external contributor pull request merge rate for infeng/react-viewer?

The external pull request merge rate is 87.5%. 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 infeng/react-viewer?

infeng/react-viewer 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 infeng/react-viewer 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.