Reading the repo — stats and the shipped feed land in about ten seconds…
APISIX Ingress Controller for Kubernetes
1.1k 392 34 openLast shipped 7d ago
APISIX Ingress Controller for Kubernetes
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 apisix-ingress-controller'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.
fix: stop logging plugin config and whole HTTPRoute/Gateway objects (#2892)
feat(apisix): attribute a GatewayProxy's global rules and plugin metadata to itself (#2885)
feat(cache): rewrite global_rules and plugin_metadata as owned rows (#2884)
feat(cache): track which Kubernetes resource owns each service, ssl and consumer (#2883)
chore(deps): bump google.golang.org/grpc from 1.82.1 to 1.83.2 (#2853)
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.
