Reading the repo — stats and the shipped feed land in about ten seconds…
Continuous Profiling Platform. Debug performance issues down to a single line of code
11.6k 793 396 openLast shipped 6h ago
Continuous Profiling Platform. Debug performance issues down to a single line of code
The week focused on keeping example applications current with dependency updates across Node.js, Go, Ruby, and .NET stacks, along with repairs to the examples CI pipeline that ensures they stay fresh. Core fixes addressed Helm RBAC discovery configuration, JFR profile size handling, and Series query…
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 pyroscope'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.
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.
