Review economics
guanzhi/GmSSL
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
#1905 修复 tool_tls13_sm4_gcm_client_cert — TLS 1.3 客户端证书选择 bug
0 reviews · 21h to merge
#1902 修复 sm4_arm64.c 和 sm3_arm64.c 中uint32x4_t 与 uint8x16_t 隐式混用导致的编译问题
0 reviews · 23h to merge
#1906 修复 tool_pqc — XMSS 类型名错误
0 reviews · 20h to merge
#1903 修复Linux arm64下链接问题
0 reviews · 22h to merge
#1871 fix(sm2): fix compressed point output writing y instead of x
0 reviews · 138.3d 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 226 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 guanzhi/GmSSL 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 guanzhi/GmSSL — 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