Point Cloud Library (PCL)
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 60%
Response Time: 17h
First Timer Success: 100%
PointCloudLibrary/pcl has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in PointCloudLibrary/pcl respond to incoming external pull requests in approximately 17.0 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 57.4 places PointCloudLibrary/pcl in the A tier.
The external contributor pull request merge rate for PointCloudLibrary/pcl is 60.0%, based on public PR activity from non-core contributors.
PointCloudLibrary/pcl does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in PointCloudLibrary/pcl. Prompt code reviews with positive guidance for new contributors.
Discussions in PointCloudLibrary/pcl focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/PointCloudLibrary/pcl?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~11 hours (75% approval). Large PRs (>500 lines) take ~82 hours (27% approval). Keep your diff compact for rapid review.
Summary Variant analysis of historical fixes in pcl identified 1 code site where an integer-overflow guard, bounds check, or safe-allocation wrapper exists at one location but is missing at a structurally identical sibling location (same file, same function, or same pattern family) elsewhere in the codebase. Each finding below is code-confirmed against the current HEAD (verified by cloning the repository fresh and checking the pattern is still present), with the exact file/line locations, the root cause, a description of the trigger path, and — where available — ASan/execution verification output or a proof-of-concept. Note on origin: these were surfaced by an automated variant-analysis pipeline that diffs historical fix commits against sibling code paths, then has each candidate manually reviewed. I'm posting them together per-project rather than as separate issues to respect maintainer time. Happy to split, close, or reprioritize any of these as you see fit. Finding 1: PCL — A
Full list: cuda/filters/include/pcl/cuda/filters/voxel_grid.h:PCL_DEPRECATED_HEADER(1, 16, "The CUDA VoxelGrid filter does not work. Use the CPU VoxelGrid filter instead.") cuda/filters/include/pcl/cuda/filters/filter.h: PCL_DEPRECATED(1, 16, "use bool getFilterLimitsNegative() instead") filters/include/pcl/filters/voxel_grid.h: PCL_DEPRECATED(1, 16, "use bool getFilterLimitsNegative() instead") filters/include/pcl/filters/voxel_grid.h: PCL_DEPRECATED(1, 16, "use bool getFilterLimitsNegative() instead") geometry/include/pcl/geometry/boost.h:PCL_DEPRECATED_HEADER(1, 16, "Please include the needed boost headers directly.") gpu/containers/src/device_memory.cpp:PCL_DEPRECATED(1, 16, "Removed in favour of c++11 atomics") outofcore/include/pcl/outofcore/boost.h:PCL_DEPRECATED_HEADER(1, 16, "Please include the needed boost headers directly.") visualization/include/pcl/visualization/boost.h:PCL_DEPRECATED_HEADER(1, 16, "Please include the needed boost headers directly.") visuali
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 PointCloudLibrary/pcl, 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 PointCloudLibrary/pcl acknowledge new external contributions in approximately 17 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.0% were successfully merged into the primary branch.
PointCloudLibrary/pcl has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~17 hours. 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 57.4 places PointCloudLibrary/pcl in the Welcoming tier.
The external pull request merge rate is 60.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
PointCloudLibrary/pcl does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for PointCloudLibrary/pcl 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.