Review economics
jetlinks/jetlinks-community
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
#762 fix(协议管理): 修复协议更新jar包时不生效的问题
0 reviews · 0h to merge
#761 feat(设备接入): 补齐设备诊断链路追踪
0 reviews · 1h to merge
#759 fix(设备管理): 补齐获取设备会话信息接口，用于设备详情->设备接入页签使用
0 reviews · 0h to merge
#757 fix: support Timestamp conversion in CommonConfiguration
0 reviews · 6h to merge
#756 build(deps): bump org.bouncycastle:bcprov-jdk18on from 1.81 to 1.84
0 reviews · 1h 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; 1 PR came off an agent branch with no commit attribution, so the real share runs higher; reads 100 of 219 merged PRs — the rest have not been analyzed yet.
Detected: OpenAI Codex.
“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 jetlinks/jetlinks-community 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 jetlinks/jetlinks-community — 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