.svg)
Codacy was running across all their repositories, gates were configured, policies were in place. What the VP of Engineering at this 130-engineer team didn't have was visibility into whether their standards were actually being enforced across every repository. When they got it, they found that nearly 30% of pull requests had merged without a completed analysis.
You can have every policy set up correctly and still have repositories where coverage was never configured, or have PRs merge before the analysis completes. The Usage Dashboard is how we help you ensure you get full value from every policy, gate, and standard you've configured on Codacy.
What's in Codacy, what's missing, and where standards are holding
The Codacy Usage Dashboard – available to customers on all plans – shows every repository connected to Codacy and how they break down across four categories:
- Repositories with both merge gates and coverage reporting configured
- Repositories without merge gates configured
- Repositories without coverage reporting configured
- Repositories with no merge gates nor coverage reports configured
- For GitHub organizations, you also see repositories in your GitHub organizations that have not been added to Codacy yet
The Merged pull requests section shows, across any time period you choose:
- What share of PRs were analyzed before merging
- What share of PRs passed their quality gates
- What share of PRs had failed gates but were merged anyway
- What share of PRs had no gates defined at all
Each metric trends over time, so you can see when things changed and which repositories are driving it. Clicking into any category surfaces the affected repositories and lets you act directly. If 40 repositories are missing gates, you can apply a policy to all of them at once rather than configuring them one by one.
See where your standards stand today
Quality and security standards enforced inconsistently are not really standards. The consequences are gradual: developers learn that gates are sometimes optional, coverage thresholds drift, and audit prep becomes a scramble to explain why the data does not match the policy.
Codacy has always given engineering leaders visibility into code health. The Usage Dashboard adds the layer above it: are gates defined, is coverage running, and is every developer's code actually being analyzed.
Log into Codacy and open the Usage Dashboard from your organization overview to see where your quality and security standards stand today.
