Autonomous software engineering fleet of AI agents for production-grade PRs on AgentField: plan, code, test, and ship.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 71%
Response Time: -
First Timer Success: 67%
Agent-Field/SWE-AF has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Agent-Field/SWE-AF 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 69.4 places Agent-Field/SWE-AF in the A tier.
The external contributor pull request merge rate for Agent-Field/SWE-AF is 70.9%, based on public PR activity from non-core contributors.
Agent-Field/SWE-AF currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Go project in Agent-Field/SWE-AF 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/Agent-Field/SWE-AF?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (89% approval). Large PRs (>500 lines) take ~115 hours (32% approval). Keep your diff compact for rapid review.
Summary Furrow mirroring is one-way today: a run publishes its workspace and a laptop clones it. There is no way to go the other direction — hand a local directory to a remote node and have build / implement_issue run against it. That is the missing half of "run my code on the fleet". Right now a remote node can only work on code it can git clone, so anything uncommitted, unpushed, private-to-my-laptop, or simply not a git repo cannot be given to a cloud SWE node at all. Everything needed to close this already exists and is deployed. The gap is one reasoner and one token path. What exists today Outbound mirroring works end-to-end. Verified against a live Railway deployment: get_workspace_handle → furrow clone over furrowd → 349 MB of a run's real working tree (sparse checkout, untracked files and all) materialized on a laptop. go/internal/furrow/manager.go — Attach, Publish, Handle, Detach, Sweep. Every entry point is outbound. Attach(runID, buildID, repoPath) takes a workspac
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 Agent-Field/SWE-AF, 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 Agent-Field/SWE-AF acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.9% were successfully merged into the primary branch.
Agent-Field/SWE-AF has a recorded first-timer success rate of 66.7%. 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 69.4 places Agent-Field/SWE-AF in the Welcoming tier.
The external pull request merge rate is 70.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Agent-Field/SWE-AF 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 Agent-Field/SWE-AF 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.