The first web framework designed for AI to write. Built on Python, FastAPI, Pydantic, and HTMX. By the authors of Two Scoops of Django.
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 33%
Response Time: 3d
First Timer Success: -
feldroy/air has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in feldroy/air respond to incoming external pull requests in approximately 69.3 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 46.3 places feldroy/air in the B tier.
The external contributor pull request merge rate for feldroy/air is 33.3%, based on public PR activity from non-core contributors.
feldroy/air currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Python project in feldroy/air 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/feldroy/air?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~45 hours (42% approval). Large PRs (>500 lines) take ~333 hours (15% approval). Keep your diff compact for rapid review.
Problem ruff.toml sets preview = true under [lint] (line 53). This opts into every unstable, experimental rule across every selected prefix. When ruff ships a new preview rule in any of Air's 30+ selected prefixes, CI can break on the next ruff upgrade without any change to the config. This is what caused the DOC201 friction in #1078. DOC201 is a preview-only rule. It only fired because preview mode is on. The rule itself wouldn't have been enforced under stable ruff. The formatter also has preview = true (line 49), which carries the same risk for formatting changes. Change Set preview = false for both [lint] and [format]. If specific preview rules are valuable, select them individually so they're a deliberate choice rather than an implicit opt-in to everything unstable.
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 feldroy/air, 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 feldroy/air acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 33.3% were successfully merged into the primary branch.
feldroy/air has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 46.3 places feldroy/air in the Solid tier.
The external pull request merge rate is 33.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, feldroy/air 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 feldroy/air 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.