Static reflection for enums (to string, from string, iteration) for modern C++, work with any enum type without any macro or boilerplate code
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 46%
Response Time: 15h
First Timer Success: 33%
Neargye/magic_enum has a recorded first-timer success rate of 33.3%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Neargye/magic_enum respond to incoming external pull requests in approximately 14.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 48.8 places Neargye/magic_enum in the B tier.
The external contributor pull request merge rate for Neargye/magic_enum is 46.2%, based on public PR activity from non-core contributors.
Neargye/magic_enum currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in Neargye/magic_enum. 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/Neargye/magic_enum?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~10 hours (58% approval). Large PRs (>500 lines) take ~71 hours (21% approval). Keep your diff compact for rapid review.
bash-5.3$ git describe --tag --dirty v0.9.8-54-g00d372c bash-5.3$ git branch develop feature/format-cmake-files feature/module_target * master module_target bash-5.3$ cmake -S . -B build/release -G Ninja -D CMAKE_BUILD_TYPE=Release -D CMAKE_CXX_STANDARD=26 ninja -C build/release ninja -C build/release test bash-5.3$ gmake env | egrep '^C' CMAKE_CONFIG_TYPE = Release CMAKE_PREFIX_PATH = /Users/clausklein/.local CMAKE_GENERATOR = Ninja CURDIR = /Users/clausklein/Workspace/cpp/magic_enum CMAKE_INSTALL_PREFIX = /Users/clausklein/.local CMAKE_CONFIGURATION_TYPES = Release;Debug CPM_USE_LOCAL_PACKAGES = NO CLASSPATH = /usr/local/opt/antlr/antlr-4.13.0-complete.jar: CMAKE_EXPORT_COMPILE_COMMANDS = YES CMAKE_CXX_COMPILER_LAUNCHER = ccache CMAKE_C_COMPILER_LAUNCHER = ccache CPM_SOURCE_CACHE = /Users/clausklein/.cache/CPM CXX = g++-16 bash-5.3$ ctest --test-dir build/release --rerun-failed --output-on-failure Test project /Users/clausklein/Workspace/cpp/magic_enum/build/release S
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 Neargye/magic_enum, 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 Neargye/magic_enum acknowledge new external contributions in approximately 14 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 46.2% were successfully merged into the primary branch.
Neargye/magic_enum has a recorded first-timer success rate of 33.3%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~14 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 48.8 places Neargye/magic_enum in the Solid tier.
The external pull request merge rate is 46.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Neargye/magic_enum 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 Neargye/magic_enum 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.