Reading the repo — stats and the shipped feed land in about ten seconds…
Enterprise Azure Policy-as-Code (EPAC) solution
550 328 23 openLast shipped 2d ago
Enterprise Azure Policy-as-Code (EPAC) solution
The team fixed several issues around policy assignment parameters, including correcting JSON parameter export and allowing parameterFile paths to exist outside the standard policyAssignments directory. Additional work addressed policy resource name validation, AMBA default configuration, and…
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 enterprise-azure-policy-as-code'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.
