Java SDK for Hiero
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 57%
Response Time: 1d
First Timer Success: 38%
hiero-ledger/hiero-sdk-java has a recorded first-timer success rate of 37.5%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in hiero-ledger/hiero-sdk-java respond to incoming external pull requests in approximately 26.6 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 54.4 places hiero-ledger/hiero-sdk-java in the B tier.
The external contributor pull request merge rate for hiero-ledger/hiero-sdk-java is 57.1%, based on public PR activity from non-core contributors.
hiero-ledger/hiero-sdk-java currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (62% critical review signals). Ensure PRs strictly follow guidelines before requesting review in hiero-ledger/hiero-sdk-java.
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/hiero-ledger/hiero-sdk-java?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~17 hours (71% approval). Large PRs (>500 lines) take ~128 hours (26% approval). Keep your diff compact for rapid review.
🆕🐥 First Timers Only This issue is reserved for people who have never contributed or have made minimal contributions to Hiero. We know that creating a pull request (PR) is a major barrier for new contributors. The goal of this issue and all other issues in find a good first issue is to help you make your first contribution to the Hiero. 👾 Description of the issue missing preposition + stray doubled colon The Java SDK for interacting a Hiero based network:: -> The Java SDK for interacting with a Hiero based network: 💡 Proposed Solution missing preposition + stray doubled colon The Java SDK for interacting a Hiero based network:: -> The Java SDK for interacting with a Hiero based network: 👩💻 Implementation Steps missing preposition + stray doubled colon The Java SDK for interacting a Hiero based network:: -> The Java SDK for interacting with a Hiero based network: ✅ Acceptance Criteria To be able to merge a pull request for this issue, we need: Signed commits: co
🆕🐥 First Timers Only This issue is reserved for people who have never contributed or have made minimal contributions to Hiero. We know that creating a pull request (PR) is a major barrier for new contributors. The goal of this issue and all other issues in find a good first issue is to help you make your first contribution to the Hiero. 👾 Description of the issue Two reference links written with parentheses, so they 404 Lines 72 and 88 both contain Discord, which markdown reads as a relative URL to a file named discord. 💡 Proposed Solution The reference is already defined at line 101 [discord]: https://hedera.com/discord and used correctly at line 92 [Discord][discord]. Fix: (discord) → [discord] on lines 72, 88. 👩💻 Implementation Steps The reference is already defined at line 101 [discord]: https://hedera.com/discord and used correctly at line 92 [Discord][discord]. Fix: (discord) → [discord] on lines 72, 88. ✅ Acceptance Criteria To be able to merge a pull
🆕🐥 First Timers Only This issue is reserved for people who have never contributed or have made minimal contributions to Hiero. We know that creating a pull request (PR) is a major barrier for new contributors. The goal of this issue and all other issues in find a good first issue is to help you make your first contribution to the Hiero. 👾 Description of the issue public static Client forMirrorNetwork(List mirrorNetworkList, long shard, long realm) The signature takes shard before realm; the javadoc documents realm first. Both are long, so a reader following the docs silently swaps them at the call site. The overload's javadoc at :213-214 has the same empty @param/@return problem. Fix: reorder and fill in descriptions. 💡 Proposed Solution public static Client forMirrorNetwork(List mirrorNetworkList, long shard, long realm) The signature takes shard before realm; the javadoc documents realm first. Both are long, so a reader following the docs silently swaps them at the call s
🆕🐥 First Timers Only This issue is reserved for people who have never contributed or have made minimal contributions to Hiero. We know that creating a pull request (PR) is a major barrier for new contributors. The goal of this issue and all other issues in find a good first issue is to help you make your first contribution to the Hiero. 👾 Description of the issue Fix typo on line 55 in BaseNodeAddress fom→from 💡 Proposed Solution Fix typo on line 55 in BaseNodeAddress fom→from 👩💻 Implementation Steps Fix typo on line 55 in BaseNodeAddress fom→from ✅ Acceptance Criteria To be able to merge a pull request for this issue, we need: Signed commits: commits must be DCO and GPG key signed All Tests Pass: our workflow checks like unit and integration tests must pass Issue is Solved: The implementation fully addresses the issue requirements as described above No Further Changes are Made: Code review feedback has been addressed and no further changes are request
🆕🐥 First Timers Only This issue is reserved for people who have never contributed or have made minimal contributions to Hiero. We know that creating a pull request (PR) is a major barrier for new contributors. The goal of this issue and all other issues in find a good first issue is to help you make your first contribution to the Hiero. 👾 Description of the issue Fix Javadoc in ContractUpdateTransaction method getMaxAutomaticTokenAssociations. Put this javadoc /** * Get the maximum automatic token associations. * * @return the max automatic token associations */ 💡 Proposed Solution Fix Javadoc in ContractUpdateTransaction method getMaxAutomaticTokenAssociations. Put this javadoc /** * Get the maximum automatic token associations. * * @return the max automatic token associations */ 👩💻 Implementation Steps Fix Javadoc in ContractUpdateTransaction method getMaxAutomaticTokenAssociations. Put this javadoc /** * Get t
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 hiero-ledger/hiero-sdk-java, 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 hiero-ledger/hiero-sdk-java acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 57.1% were successfully merged into the primary branch.
hiero-ledger/hiero-sdk-java has a recorded first-timer success rate of 37.5%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 54.4 places hiero-ledger/hiero-sdk-java in the Solid tier.
The external pull request merge rate is 57.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, hiero-ledger/hiero-sdk-java 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 hiero-ledger/hiero-sdk-java 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.