Reading the repo — stats and the shipped feed land in about ten seconds…
Enterprise Azure Policy-as-Code (EPAC) solution
555 332 19 openLast shipped 8d ago
Enterprise Azure Policy-as-Code (EPAC) solution
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.
Showing raw commit titles for the newest commits. Sign in to generate AI summaries.
updating policyEnrollment warnings to informational in build-deploymentplans (#1415)
Make policy assignment name length validation scope-aware (24 chars at MG, 64 at Sub/RG) (#1411)
Fail plan build when a policy assignment name exceeds 24 characters (#1410)
Filter Policy Set role assignments by effect and honour definitionVersion (#1395)
Fix assignment file collection when only one .json or .jsonc file exists (#1399)
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.
