ClusterDuck Protocol
/All repositories
We updated our Health Score methodology! Read more about it in our docs and join the discussion on GitHub.
Maintainer coverage is the primary crisis signal. Development cadence shows little to offset it. Every health signal is at or near zero. Security & Supply Chain is unavailable, so weights were redistributed.
Consistent commits, responsive maintainers, regular releases, and healthy issue triage.
Health breakdown
Maintainer availability, known risks and supply chain posture, and whether the project is actively developed or appropriately stable.
Median response time is 2 days, but most repositories have response times over 90 days.
3 active maintainers currently have merge rights.
Contributors come from 14 organizations only.