The Unified and Autonomous Development Platform
The week focused on modernizing Docker build tooling and tightening validation across job execution. The Docker executor layer was refactored to use buildx and add enhanced security settings, while a new Buildx Image Tools step and improved registry login handling were introduced. Separately, fixes…
Get this in your inbox every Monday →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 onedev'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.
refactor: Replace RegistryToolStep with CraneStep and enhance Docker command handling
refactor: Rename image build settings to reflect buildx usage in Docker executors
refactor: Update security settings descriptions in JobExecutor and ServerDockerExecutor
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.