Quantify tech debt — Track incremental improvements — Monitor regressions
Common problems with keeping track of technical quality:
- When tech debt is invisible, it's difficult to plan much-needed maintenance efforts 🔧
- Individual tools measure different metrics, inability to combine them leads to
a lack of comprehensive overview 🧑🦯 - Open-source tools typically used for failing checks in CI, which can't measure incremental improvements due to arbitrary pass/fail thresholds 🤖
- Off-the-shelf solutions tend to be opinionated and hard to customize, so may not fit your specific needs 🧱
We want to change that!
| 🚀 Get started️ | 🤖 CI automation |
|---|---|
![]() |
![]() |
|
|
| 📈 Portal️ | 🔌 Custom plugins |
|---|---|
![]() |
![]() |
|
|
| Icon | Name | Description |
|---|---|---|
| ESLint | Static analysis using ESLint rules. | |
| Code Coverage | Collects code coverage from your tests. | |
| JS Packages | Checks 3rd party packages for known vulnerabilities and outdated versions. | |
| Lighthouse | Measures web performance and best practices with Lighthouse. | |
| JSDocs | Analyzes how much source code is documented using JSDocs comments. | |
| TypeScript | Checks for TypeScript errors using strict compiler flags. |
-
Configure
Pick from a set of supported packages or include your own ideas. 🧩 -
Integrate
Use our integration guide and packages to set up CI integration in minutes. ⏱️ -
Observe
Guard regressions and track improvements with every code change. 🔍 -
Relax!
Watch improvements, share reports 📈
- Read how to contribute to the codebase. See: CONTRIBUTING.md 🤝




