Review economics
swiftlang/swift
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.
—
Attributed
0
Attributed PRs
100
Other PRs
100
Read
The rest — the latest 5
#91212 [Embedded] Extend key path support to multi-component key paths with computed properties and captures
1 reviews · 41h to merge
#91241 Reapply "[stdlib] Fix Atomic.min/max using signed comparison on unsig…
1 reviews · 22h to merge
#91147 [Concurrency] Remove prohibition on actors conforming to isolated protocols
1 reviews · 4.8d to merge
#91070 [StrictSafety] Add @unsafe(always) to always trigger error
23 reviews · 7.1d to merge
#91202 Runtime,RemoteInspection: add COM existential metadata and value witness
1 reviews · 46h to merge
How this was measured
No commit in this window carries agent attribution, so there is no AI-authored share to read here — which is not evidence there is none; tools that only complete code inline leave no commit trail, so the unattributed side includes AI-assisted work; reads 100 of 60451 merged PRs — the rest have not been analyzed yet.
“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 swiftlang/swift 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 swiftlang/swift — 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