A blazingly fast multi-language serialization framework for idiomatic domain objects, schema IDL, and cross-language data exchange.
C-Rank Grade: A (Welcoming) - 70/100
External PR Merge Rate: 89%
Response Time: -
First Timer Success: 82%
apache/fory has a recorded first-timer success rate of 81.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in apache/fory 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.
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 70.0 places apache/fory in the A tier.
The external contributor pull request merge rate for apache/fory is 89.1%, based on public PR activity from non-core contributors.
apache/fory currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in apache/fory. Prompt code reviews with positive guidance for new contributors.
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/apache/fory?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (40% approval). Keep your diff compact for rapid review.
Question Hi. Does Apache Fory support field validation inside *.fdl , similar to Protobuf tools (Protovalidate (CEL)/protoc-gen-validate (PGV)) ❓ https://fory.apache.org/docs/compiler/protobuf_idl_support/ syntax = "proto3"; package v1.user; import "buf/validate/validate.proto"; message UserProfile { string id = 1 [(buf.validate.field).string.uuid = true]; // Numeric boundaries uint32 age = 2 [(buf.validate.field).uint32.gte = 18, (buf.validate.field).uint32.lte = 120]; string email = 3 [(buf.validate.field).string.email = true]; // Length constraints and regex pattern matching string username = 4 [ (buf.validate.field).string.min_len = 3, (buf.validate.field).string.max_len = 30, (buf.validate.field).string.pattern = "^[a-zA-Z0-9_]+$" ]; // Collection constraint (ensure list contains at least one item) repeated string roles = 5 [(buf.validate.field).repeated.min_items = 1]; // Standard rules handle simple single-field checks. uint64 amount
Feature Request format generated code by header and line break Is your feature request related to a problem? Please describe No response Describe the solution you'd like add a comment to begin of generted file: generated by apache fory compiler for too long line, add break, limit each line max width to 80, be causious to python indent newline and c++ macro Describe alternatives you've considered No response Additional context #3099
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 apache/fory, 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 apache/fory acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 89.1% were successfully merged into the primary branch.
apache/fory has a recorded first-timer success rate of 81.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 70.0 places apache/fory in the Welcoming tier.
The external pull request merge rate is 89.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, apache/fory currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for apache/fory 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.