One number.
Your team's full health.
The Friction Score is a single 0–100 metric that reflects how much engineering friction your team is carrying right now. It's computed from real signals — CI failures, stale PRs, deployment issues, flaky tests — and updates in real time.
Current Friction Score
Lower is better · 0 = no friction, 100 = critical
2
Critical signals
5
High signals
8
Medium signals
What's measured
Five signal types, each weighted by impact. Computed over the last 7 days.
CI Failures
Repeated CI failures on main branches drive the score up fast.
Stale PRs
PRs sitting unreviewed for more than your threshold drag velocity down.
Deployment Failures
Failed Vercel or CI deployments increase instability signals.
Flaky Tests
Alternating pass/fail patterns are detected and factored in.
Code Debt (TODOs)
FIXME/TODO/HACK/XXX patterns found on every push.
Score ranges
What each range means for your team.
Team is shipping cleanly. Keep it up.
Some friction present. Worth addressing soon.
Friction is slowing the team. Act now.
Engineering is under heavy load. Immediate action needed.
Trend over time
Watch your score drop as Deviera helps your team resolve friction patterns one by one.
Triggers automations
A rising score can automatically trigger new automation rules — escalate, notify, or create issues.
Weekly health report
Get a weekly email summarising your score, top signals, and time saved. Share it with leadership.
What's your team's score?
Connect GitHub and get your Friction Score in under 5 minutes.
Get my score free