Review economics
apache/airflow
Read from the 100 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
≥2%
Attributed
a floor
2
Attributed PRs
98
Other PRs
100
Read
Attributed — the latest 2
The rest — the latest 5
#71169 [v3-3-test] Add support for pandas 3 based xcoms in airflow (#71103)
0 reviews · 7h to merge
#70167 Align Dag Runs docs with Airflow 3 trigger timetable defaults
13 reviews · 15.4d to merge
#71182 Revert the pandas < 3 cap for DataFrame XComs (backport of #71100)
1 reviews · 2h to merge
#71183 [v3-3-test] Fail task instances whose stored next_kwargs cannot be processed (#70685)
2 reviews · 1h to merge
#71184 [v3-3-test] Fix ambiguous git refspec when pushing release-candidate constraints (#71181)
0 reviews · 0h to merge
How this was measured
2% of merged commits carry agent attribution — a floor, not the share; tools that only complete code inline leave no commit trail, so the unattributed side includes AI-assisted work; reads 100 of 39318 merged PRs — the rest have not been analyzed yet.
Detected: Claude Code, GitHub Copilot coding agent.
“Attributed” means a commit carried an agent’s signature — a co-author trailer, an agent commit identity, or an agent bot account. Tools that only complete code inline leave no such mark, so the other column is “rest”, not “human-written”. Full method and its limits
The badge reads this repo’s current report, so it follows the number.
Tell me when this moves
We re-read apache/airflow weekly and email only when the number changes materially.
Read your own repos
This one is public. For a private repo, run the same read locally through your own GitHub credentials — nothing is installed and nothing is sent to us.
npx @ambera/review-taxWant this continuously on apache/airflow — each pull request paired to the task it came from, and the work graded from its review loop rather than its diff size? Claim this repo in Forge
Browse every repo people have read · Read a different repository