Official Python SDK for the Agent2Agent (A2A) Protocol
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 31%
Response Time: 5h
First Timer Success: 63%
a2aproject/a2a-python has a recorded first-timer success rate of 62.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in a2aproject/a2a-python respond to incoming external pull requests in approximately 5.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.8 places a2aproject/a2a-python in the A tier.
The external contributor pull request merge rate for a2aproject/a2a-python is 30.8%, based on public PR activity from non-core contributors.
a2aproject/a2a-python currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in a2aproject/a2a-python welcoming community pull requests and bug fixes.
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/a2aproject/a2a-python?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 10:00 UTC (10: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 ~4 hours (38% approval). Large PRs (>500 lines) take ~26 hours (15% approval). Keep your diff compact for rapid review.
Problem When implementing streaming text output via TaskArtifactUpdateEvent, the current new_text_artifact utility generates a fresh UUID for artifact_id on every call. This makes it impossible to use append=True correctly, since append semantics require a stable artifact_id across chunks. The sample travel_planner_agent demonstrates this problem — it calls new_text_artifact in a loop: async for event in self.agent.stream(query): message = TaskArtifactUpdateEvent( contextId=context.context_id, taskId=context.task_id, artifact=new_text_artifact( name='current_result', text=event['content'], ), ) await event_queue.enqueue_event(message) Each iteration produces a new artifact_id, so clients cannot merge chunks into a single artifact. This results in N separate artifact cards in the UI instead of one progressively streamed response. Describe the solution you'd like Add a stateful streaming helper to a2a.utils that: Gene
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 a2aproject/a2a-python, 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 a2aproject/a2a-python acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 30.8% were successfully merged into the primary branch.
a2aproject/a2a-python has a recorded first-timer success rate of 62.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 57.8 places a2aproject/a2a-python in the Welcoming tier.
The external pull request merge rate is 30.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, a2aproject/a2a-python 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 a2aproject/a2a-python 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.