Quantify tech debt β Track incremental improvements β Monitor regressions
version release date NodeJS support license commit activity CI Codecov
Type safety Bug prevention Code style Code coverage Security Updates Documentation
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 |
|---|---|
| Getting started cover image | CI Automation cover |
|
|
| π PortalοΈ | π Custom plugins |
|---|---|
| Portal integration cover image | 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 π€