Automated, reproducible metrics for the Apache Cassandra project.
Metrics for the Apache Cassandra project. Definitions follow CHAOSS where one exists.
CHAOSS Starter Project Health metrics model
Computed for Cassandra from three venues, shown separately: GitHub PR time to first review, JIRA time to first response, and dev@ time to first reply.
JIRA
1.8 days Sep 2026 · n=48 backfill pending
Based on: CHAOSS: Time to First Response, CHAOSS: Responsiveness practitioner guide
Computed for Cassandra from two venues, shown separately, since reviewed changes are committed via JIRA as well as GitHub: GitHub pull requests, and JIRA issues entering Patch Available (Cassandra's patch-submission equivalent of a change request).
This project's existing contributor_absence_factor metric: the smallest number of contributors whose combined trailing-12-month commits reach 50% of all commits.
This project's existing release_frequency metric: count of GA releases (collectors/release.py: git tags, excluding alpha/beta/rc) in the trailing-24-month window ending each completed month.
| Line | Next targeted version | CI |
|---|---|---|
| 6.0 | 6.0-alpha3 | UNSTABLE |
| 5.0 | 5.0.10 | UNSTABLE |
| 4.1 | 4.1.13 | UNSTABLE |
| 4.0 | 4.0.22 | UNSTABLE |
| 3.11 | 3.11.20 | UNSTABLE |
| 3.0 | 3.0.33 | UNSTABLE |
n/a
Code and contributor health: sustainability, review capacity, and responsiveness.
+43 more metrics
Mailing-list metrics, computed from metadata only — never message content.
+7 more metrics
Per-commit facts from the public record — reviewers, CI evidence, checkstyle.
+2 more metrics