DORA Metrics
Open Reviews → DORA to inspect four CodeStax review-velocity indicators derived from pull-request review records. These are DORA-like product heuristics, not the official DORA industry benchmark and not the separate organization-wide Metrics dashboard.
The four indicators
Review frequency
How often CodeStax completes pull-request reviews in the selected period.
Why it matters: Teams that review frequently catch issues earlier and ship smaller, safer changes.
How it is calculated: completed PR reviews divided by the selected number of days. Scans and developer counts are not included.
Average lead time
Time from creation of the CodeStax review record to completion.
Why it matters: Long lead times mean developers wait days for security feedback, leading to context-switching and delayed fixes.
How it is calculated: average time between CodeStax review creation and completion. This measures the CodeStax review record, not commit-to-production lead time.
High-risk review rate
Percentage of completed reviews with a stored risk score of 60 or greater.
Why it matters: A high failure rate indicates gaps in secure coding practices, missing pre-commit checks, or inadequate developer training.
How it is calculated: completed reviews with a risk score of 60 or greater divided by all completed reviews in the selected period. The API field remains change_failure_rate for compatibility.
Mean time to review
Average stored analyzer duration for completed reviews.
Why it matters: Slow reviews block merges and slow down the entire development pipeline.
How it is calculated: average stored review scan duration, in seconds, for completed reviews.
Dashboard views
Weekly chart
Choose 7, 30, 90, or 365 days. The dashboard shows summary cards and a weekly breakdown of completed review count and average risk score.
Summary cards
Four cards at the top of the page show:
- Current value for each metric
- A CodeStax
good,moderate, orpoorheuristic where the card supports one
Use the indicators effectively
- Compare the same repository and date window over time.
- Treat lead time and mean time to review as CodeStax workflow indicators, not deployment metrics.
- Pair a rising high-risk review rate with feedback insights and finding categories.
- Use the separate Metrics dashboard for organization productivity summaries and leaderboard data.
CLI access
Retrieve DORA metrics programmatically:
$ codestax dora --repo-id <repo_id> --days 30See CLI Reference for full usage.
API access
curl -H "X-API-Key: $CODESTAX_API_KEY" \
"https://codestax.co/api/reviews/dora?repo_id=<repo_id>&days=30"days must be between 7 and 365. Omit repo_id for all repositories in the current organization. The response includes the four current values, review totals, average risk, and weekly breakdown; it does not return official DORA ratings.