Is master safe to run today? This page reads SonarCloud and GitHub as you open it — quality gate, coverage, CI, what has changed since the last release, and the commits going in. Nothing here is typed by hand.
Quality and CI numbers are at most two minutes old.
Four checks against master. The light is green only when all four pass.
The current SonarCloud scan of master.
Every scan SonarCloud has kept, oldest on the left. Hover a chart for the exact value and time.
Lines added and removed in the repository each week.
Days between each of the last releases and the one before it.
Amber means nothing is wrong, but something has not finished. Either the latest CI run is still going, or SonarCloud has not yet scanned the newest commit. It turns green by itself, usually within ten minutes of a push.
GitHub only lists the first 300 files of a comparison, so a very large gap shows as 300+. The commit count is exact.
SonarCloud only keeps the scans it has run. The coverage and smell history begins with the first scan; the commit and churn charts come from GitHub and go back years.
Master. The release is shown only as the baseline to compare against, so you can see how far master has moved since the version you may be running.
This page and its endpoints were described, generated, verified and deployed without a build step. The same platform runs your own backend — database, secured API, authentication and frontend hosting — on your own hardware or hosted by us.
Hyperlambda