An open source benchmarking framework for IT automation
A deterministic 0–100 hygiene score — README, license, CI, tests, docs, and freshness.
Who ships this repo — author concentration and the bus factor across the last 300 mainline commits.
How welcoming this repo is to contributors — issue throughput, close time, responsiveness, and good-first-issue count.
What this project is built on — dependency count by ecosystem, the license mix, and anything worth a legal look before you adopt it.
Whether this project's CI can be trusted — pass rate, run times, flaky runs, and which workflow is the weak link.
Grounded in ITBench's README, structure, and recent commits — answers won't invent code they haven't seen.
A Monday email with what shipped, in plain English — no account needed.
Showing raw commit titles for the newest commits. Sign in to generate AI summaries.
chore(deps): update registry.access.redhat.com/ubi10/python-314-minimal docker tag to v10.2-1790644442 (#1267)
chore(deps): update docker.io/clickhouse/clickhouse-server docker tag to v26.9.10 (#1269)
chore(deps): update registry.access.redhat.com/ubi10/go-toolset docker tag to v1.26.7-1790644709 (#1266)
chore(deps): update module go.opentelemetry.io/collector/cmd/builder to v0.162.0 (#1264)
chore(deps): update quay.io/prometheus/prometheus docker tag to v3.15.0 (#1265)
chore(deps): update opentelemetry collector builder dependencies (#1261)
A floor, not a guess: counts only commits whose author, co-author trailer, or message explicitly credits an AI tool (Claude, Copilot, Cursor, aider, Codex…). Based on 30 mainline commits. Unattributed AI code isn't counted here — the full audit estimates that separately.