Community driven, reusable components for distributed apps
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 48%
Response Time: 1d
First Timer Success: 29%
dapr/components-contrib has a recorded first-timer success rate of 29.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dapr/components-contrib respond to incoming external pull requests in approximately 30.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 57.1 places dapr/components-contrib in the A tier.
The external contributor pull request merge rate for dapr/components-contrib is 47.7%, based on public PR activity from non-core contributors.
dapr/components-contrib currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in dapr/components-contrib.
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/dapr/components-contrib?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~20 hours (60% approval). Large PRs (>500 lines) take ~146 hours (21% approval). Keep your diff compact for rapid review.
Summary The conversation.anthropic component cannot use any Claude model newer than the 4.6 generation. Two separate problems in the pinned github.com/tmc/langchaingo are responsible, and bumping the dependency currently makes things worse rather than better. Pinned version: v0.1.15-0.20251029190607-e35755df7084 (2025-10-29). Problem 1: temperature is always serialized llms/anthropic/internal/anthropicclient/messages.go: type messagePayload struct { Model string `json:"model"` Messages []ChatMessage `json:"messages"` System string `json:"system,omitempty"` MaxTokens int `json:"max_tokens,omitempty"` StopWords []string `json:"stop_sequences,omitempty"` Stream bool `json:"stream,omitempty"` Temperature float64 `json:"temperature"` // <-- no omitempty Tools []Tool `json:"tools,omitempty"` TopP float64 `json:"top_p,omitempty"` ... } Temperature is the on
ok github.com/dapr/components-contrib/middleware/http/wasm 0.025s coverage: 53.2% of statements --- FAIL: Test_EndToEnd (0.50s) --- FAIL: Test_EndToEnd/http (0.15s) --- FAIL: Test_EndToEnd/http/consoleLog_multiple_requests (0.07s) e2e_test.go:117: Error Trace: /home/runner/work/components-contrib/components-contrib/middleware/http/wasm/internal/e2e_test.go:117 /home/runner/work/components-contrib/components-contrib/middleware/http/wasm/internal/e2e_test.go:222 Error: "time=\"2026-01-22T17:33:29.829454094Z\" level=info msg=\"main ConsoleLog\" instance=runnervmmtnos scope=Test_EndToEnd type=log ver=unknown\ntime=\"2026-01-22T17:33:29.829712916Z\" level=info msg=\"main ConsoleLog\" instance=runnervmmtnos scope=Test_EndToEnd type=log ver=unknown\ntime=\"2026-01-22T17:33:29.829831528Z\" level=info msg=\"request[0] ConsoleLog\" instance=runnervmmtnos scope=Test_EndToEnd type=log ver=unknown\nt
ok github.com/dapr/components-contrib/middleware/http/wasm 0.024s coverage: 53.2% of statements --- FAIL: Test_EndToEnd (0.56s) --- FAIL: Test_EndToEnd/http (0.17s) --- FAIL: Test_EndToEnd/http/consoleLog_stdout_and_stderr (0.07s) e2e_test.go:90: Error Trace: /home/runner/work/components-contrib/components-contrib/middleware/http/wasm/internal/e2e_test.go:90 /home/runner/work/components-contrib/components-contrib/middleware/http/wasm/internal/e2e_test.go:222 Error: "time=\"2026-01-19T19:19:44.306988448Z\" level=info msg=\"main ConsoleLog\" instance=runnervmmtnos scope=Test_EndToEnd type=log ver=unknown\ntime=\"2026-01-19T19:19:44.307263319Z\" level=info msg=\"main ConsoleLog\" instance=runnervmmtnos scope=Test_EndToEnd type=log ver=unknown\ntime=\"2026-01-19T19:19:44.307384567Z\" level=info msg=\"request[0] ConsoleLog\" instance=runnervmmtnos scope=Test_EndToEnd type=log ver=unknown\ntim
https://github.com/dapr/components-contrib/actions/runs/21047913930/job/60526999153#step:19:14084 RELEASE NOTE: FIX: Bug in bindings.kafka certification tests
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 dapr/components-contrib, 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 dapr/components-contrib acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 47.7% were successfully merged into the primary branch.
dapr/components-contrib has a recorded first-timer success rate of 29.4%. Repositories ranked Welcoming 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 57.1 places dapr/components-contrib in the Welcoming tier.
The external pull request merge rate is 47.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, dapr/components-contrib 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 dapr/components-contrib 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.