Reading the repo — stats and the shipped feed land in about ten seconds…
Nub shipped version 0.9.6 this week, featuring runtime improvements to libuv's threadpool isolation and latency measurement tooling for saturated systems. The release also landed iterator polyfill updates to match Stage 4 specs, dependency resolution fixes in aube for URL tarballs and peer…
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 nub'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.
runtime: --test, --check and -e no longer evaluate the file to look for a fetch handler (#999)
winget: the fixture tracks 0.9.6 and keeps nubr on its own bin\nubr.exe (#996)
aube: resolve URL-tarball optionals, peers and platforms; fix two nub.lock round-trips (#963)
runtime: iterator chunking/includes/join polyfills follow the Stage 4 spec (#988)
release: hold the run on the release-approval environment until the staged versions are approved (#981)
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.
