Refine high-quality datasets and visual AI models
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 70%
Response Time: 5d
First Timer Success: 65%
voxel51/fiftyone has a recorded first-timer success rate of 65.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in voxel51/fiftyone respond to incoming external pull requests in approximately 114.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 64.5 places voxel51/fiftyone in the A tier.
The external contributor pull request merge rate for voxel51/fiftyone is 70.2%, based on public PR activity from non-core contributors.
voxel51/fiftyone currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Refine high-quality datasets and visual AI models
Balanced & professional review environment in voxel51/fiftyone. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/voxel51/fiftyone?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~75 hours (88% approval). Large PRs (>500 lines) take ~551 hours (32% approval). Keep your diff compact for rapid review.
🗃️ Describe the problem In the App, filtering a Keypoint / Keypoints list attribute such as confidence with the numeric range slider can hide all points even when some values fall inside the intended range. Expected: Dragging the min thumb above the lower bound while leaving max at the upper bound keeps points whose confidence is ≥ min (and ≤ the field max). Actual: That filter often shows no points. Filtering only the upper end (e.g. max ≈ 0.4 with min at the lower bound) still works and shows the low-confidence points. Root cause (investigation): The range slider stores null when a thumb sits on a field bound (RangeSlider onMinCommit / onMaxCommit). Per-point keypoint filtering in skeletonFilter compared values with: value >= range[0] && value <= range[1] In JavaScript, null coerces to 0, so a stored range like [0.2, null] becomes value <= 0 and drops every positive confidence. Other numeric filters already handle null ends via helperFunction in pathFilters/numeric.ts; key
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to voxel51/fiftyone, 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 voxel51/fiftyone acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.2% were successfully merged into the primary branch.
voxel51/fiftyone has a recorded first-timer success rate of 65.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 64.5 places voxel51/fiftyone in the Welcoming tier.
The external pull request merge rate is 70.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, voxel51/fiftyone currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for voxel51/fiftyone 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.