Know how your team's components are doing without stitching together three dashboards and a spreadsheet. One workspace score, drill down when you need to.
The Overview dashboard shows Overall Health, 5 category scores with trends, severity distribution, and a component score radar — all on one page. This is the page you open Monday morning. The page you share in your engineering standup. The answer to "how's our quality?" that doesn't require a 30-minute preamble.
The Components view shows every component with scores per category, last activity date, and trend indicators. Sort by overall score to find what needs attention. Filter by type (API, WEB, Service) to compare like with like. Identify which component has been declining and which improved after that refactoring sprint.
The Score Trend chart shows your workspace's quality direction over 7, 30, or 90 days. See the impact of that security initiative. Measure whether onboarding new engineers affected quality. Show leadership that the investment in testing is paying off — with a chart, not an anecdote.
The overview surfaces Key Insights and Actionable Findings — the things that matter most across your team's components. Not every finding, not a flood of minor issues. The ones that affect your scores, your release readiness, and your team's ability to ship confidently.
Quality gates show which components are release-ready and which aren't — and exactly why. When your PM asks "is the release on track?" you don't hedge. You show them the gates: these three components pass, this one needs Security attention, here's what the team is fixing. Evidence, not gut feel.
Monday standup
You open the Overview dashboard. Overall Health is 8.3, up from 7.9 last month. Security improved after the dependency update push. Trust dipped slightly — you notice one component's autonomous agent contributions increased but human review time decreased. Classic delegate-without-review pattern. You flag it to the tech lead.
Wednesday
A release is planned for Friday. You check the gates: 4 of 5 components pass. The fifth has a Hygiene finding — missing branch protection on the new repo. The developer gets a finding with remediation steps and fixes it in 10 minutes.
Friday
All gates pass. You approve the release with confidence, knowing the scores back up the decision. The approval is logged with your name, the scores at the time, and the timestamp.
One score. Five categories. Full visibility from workspace to component to version.