Keep Tabs on the State of your Code with Badges

Status badges allow your teams to keep an eye on the health of their projects and their individual architectural components at a glance. They can be integrated into any tool, but are most frequently embedded on GitHub’s README pages.

CodeScene auto-generates the badges and the links for you.

Types of Badges

CodeScene currently supports badges for the following metrics:

Code Health

The Code Health status badge:

The Code Health status badge

Fig. 175 The overall code health of the project.

System Mastery

The System Mastery status badge:

The System Mastery status badge

Fig. 176 Keep track of knowledge loss when developers leave the project.

Missed Goals

The Missed Goals status badge:

The Missed Goals status badge

Fig. 177 The status of your project goals.


Status badges can be activated on a per-project and per-metric basis in the “Status Badges” configuration tab. In addition to project-level badges the Code Health and System Mastery badges can also be shown for every individual architectural component in the project. These badges are activated using the same checkbox that activates the project-level badge and their URLs can be obtained by selecting component name from the drop-down menu on the configuration screen.


CodeScene’s status badges can be embedded anywhere, as long as a network connection to the CodeScene service is available. In typical use cases, this would include pages on your organisation’s intranet, and GitHub pages.

HTML and Markdown snippets are available on the “Status Badge” configuration page when you select a badge type:

CodeScene generates markup and HTML for status badges.

Fig. 178 CodeScene generates markup and HTML for status badges.


When they are activated, CodeScene’s status badges are public. Users who are not logged in to CodeScene will still be able to see be able to see the badges. This is why badges are opt-in.

Activating a badge does not expose any other data besides the SVG image itself.