Framework for authoring workflows and activities running on top of the Cadence orchestration engine.
C-Rank Grade: B (Solid) - 58/100
External PR Merge Rate: 83%
Response Time: 12h
First Timer Success: 50%
cadence-workflow/cadence-go-client has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in cadence-workflow/cadence-go-client respond to incoming external pull requests in approximately 12.4 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 58.0 places cadence-workflow/cadence-go-client in the B tier.
The external contributor pull request merge rate for cadence-workflow/cadence-go-client is 83.3%, based on public PR activity from non-core contributors.
cadence-workflow/cadence-go-client does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Collaborative maintainer environment in cadence-workflow/cadence-go-client. Reviews community pull requests with focus on project quality.
Discussions in cadence-workflow/cadence-go-client 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/cadence-workflow/cadence-go-client?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 Tuesday - Thursday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (96% approval). Large PRs (>500 lines) take ~59 hours (38% approval). Keep your diff compact for rapid review.
Describe the bug Go SDK would time out an activity if the activity type is unknown (not registered) to the worker. Activity worker would silently fail the tasks and let the activity time out on the server. The behavior is different in Java SDK, which would respond failures immediately. Cause is due to: func (atp *activityTaskPoller) ProcessTask(task interface{}) error { // Process the activity task. request, err := atp.taskHandler.Execute(atp.taskList.GetName(), activityTask.task) if err != nil { metricsScope.Counter(metrics.ActivityExecutionFailedCounter).Inc(1) return err // <- silent failure on SDK with loggings only } cadence-go-client/internal/internal_task_pollers.go Lines 1166 to 1167 in 70ea3b3 // Process the activity task. request, err := atp.taskHandler.Execute(atp.taskList.GetName(), activityTask.task) To Reproduc
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 cadence-workflow/cadence-go-client, 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 cadence-workflow/cadence-go-client acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.3% were successfully merged into the primary branch.
cadence-workflow/cadence-go-client has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 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 58.0 places cadence-workflow/cadence-go-client in the Solid tier.
The external pull request merge rate is 83.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
cadence-workflow/cadence-go-client 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 cadence-workflow/cadence-go-client 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.